-
Posts
6,688 -
Joined
-
Last visited
-
Days Won
839
Everything posted by Paul
-
Service Should Renew When Paid, Not When Invoiced
Paul replied to PhatPixel's topic in Feature Requests
Yes, I've moved it to the feature request forum. PauloV's suggestion seems most feasible. The way renew dates are handled internally to Blesta cannot be changed, however the way they are displayed to customers would be much simpler to change. -
Are you running 5.2 or 5.3? If 5.3, I wonder if something changed and our importer is no longer able to find the domains.
-
Yeah sorry, I copy/pasted the debug information for the Blesta 2.5 import file. For the WHM** 5.2 importer, there is a debug check box that you can select to put it into debug mode, no code changes necessary. Have you tried that?
-
Node Groups were added in 3.1, as part of CORE-832. You can set a node group on the package level and let SolusVM decide which node to put the VPS on, managing the node membership through SolusVM. We also have plans to allow extra IPs to be ordered via a configurable option. A config option can be set up to request this, but it doesn't currently provision the extra IPs with the order. The module just needs to be updated to expect a specific field name for this. I'd be happy to work with you on this feature if you are able to test it.
-
If you can get HB into WHM** and then import to Blesta, that would be the best way to go since we don't have an importer for HB yet. Regarding the missing domains, did you get any errors during import? You might try debugging by making a couple changes to the code.. Try the following to enable debugging during import. Then attempt to import again from a fresh database. Open /config/blesta.php and change (line 11): Configure::errorReporting(0); to Configure::errorReporting(-1); Then open /plugins/import_managers/components/migrators/blesta/2.5/blesta2_5.php and change (lines 199-201): //echo $e->getMessage(); //echo $e->getTraceAsString(); //continue; to: echo $e->getMessage(); echo $e->getTraceAsString(); die; And then let us know if you get any errors. There may be something that's hanging these up from being imported that's different than anything we've encountered yet.
-
See CORE-961, it will be in 3.2, it's already completed.
-
When you record a payment manually, there is an "Email Receipt" checkbox. Selecting this will send a similar email to automatic credit card receipts. This aren't PDFs, though the invoice will show PAID on it if it's been paid. Some people have requested that invoices show all payments on them, which is a possibility for a future release.
-
Yeah, I wouldn't put the word bounty in it, many people assume there is a monetary award. In theory the plugin sounds like a good idea, but don't forget that they first have to install it. Most people won't go through the effort.
-
CORE-1109 - This should be shipping with Blesta 3.2.
-
We already have a policy for security related issues. See http://docs.blesta.com/display/support/Responsible+Disclosure+Policy Emailing our security department automatically opens a ticket, and we review all reports right away. We do not currently have a bounty program though. We give credit but not monetary rewards for reporting security issues. We may offer bounties in the future but we have found that most people do not download and install Blesta and test it themselves.. they run automated penetration tests on our live systems and cause headaches for our infrastructure.
-
Haha, nice mock up. This would likely be its own plugin should we build it. Since nothing is ever as simple as it first seems, what features would be in this? Custom fields? Email to 1 or more addresses? (Enter addresses via the plugin, or select the staff members instead?)
-
No alpha, you will have access to the beta though. As usual, beta's are open to all customers.
- 57 replies
-
- bootstrap
- client area
-
(and 1 more)
Tagged with:
-
Cody is working on finishing up the conversion of the order form to bootstrap. Then he is going to implement the new ajax order template that I created, which looks great btw. Then beta will start. The new order form has comparison boxes or a slider for package selection. I think most people will use the new one.
- 57 replies
-
- bootstrap
- client area
-
(and 1 more)
Tagged with:
-
How would you like to see this work? A new icon on the portal page that takes you to a contact form?
-
Very nice, sounds like it's going to be out soon also.
-
Dennis is a great guy, had the pleasure of meeting him in person last year. Very down to earth, always a pleasure to read the WHT newsletters he sends out.
-
They think you're a shill? Our only association is that you're a customer, and we did not and never will ask you or anyone to post on WHT on our behalf. If our customers aren't allowed to post on WHT on their own accord, then we're being unfairly targeted. I don't know what you originally posted, but I suggest asking for the ticket to be escalated and reviewed by SoftwareReview. Sounds like you omitted some information that you should have included, but I don't believe it's shilling because you had nothing to gain, and you posted it on your own. A mistake? Probably. A clear shilling violation? I don't think so. EDIT: I feel like promoting the chat plugin you wrote now.
-
You can upgrade/downgrade services for a client from the Manage link for their service on their client profile page. As soon as proration is added, clients will be able to upgrade/downgrade from the client area. The upgrade/downgrade packages available are those packages that are in the same package group as the package they originally ordered.
-
The marketplace will be responsible for handling updates to extensions (modules, gateways, plugins) and the built in updater would update the core only. At least I think that's the plan. Whether extensions are updated automatically or not is a separate discussion, but we're starting with the core. Still, the good news about how the marketplace should work is that even if you upgrade an extension manually.. it should be as easy as clicking a button. Just for me, personally.. I'd prefer to manually update extensions by clicking the button in the marketplace. For the core, I'd want patches installed automatically and I'd like to click a button to upgrade a minor/major release.
-
If you haven't, I'd suggest opening a ticket in their helpdesk to contest it. If the banning moderator responds, ask for it to be escalated to SoftwareReview. A permanent ban for that post seems ridiculous, especially since you have nothing to gain monetarily. (It's a free plugin!!) Maybe you should have mentioned that you wrote the plugin for full disclosure, but a perma ban for that seems absurd.. unless there were other reasons involved in their decision. Here's my suggestion to everyone who participates on WHT: 1. Follow their rules. 2. If you feel you've been unjustly targeted or given an infraction because of a post, open a ticket in their helpdesk and contest it. (I have opened a ticket every time I received an infraction, and have had one reversed) 3. If you see other people self promoting or not following the rules, report those posts. (I have reported posts made by our competitors for self-promotion, and their posts have been removed) The moderators at WHT believe they are enforcing the rules fairly. In most cases, they probably are, but because of our competitions long history and position in the market they are favored. WHT even promoted a thread for one of our competitors beta release announcements. They have never given us the courtesy. Things are changing, but it takes time. We're going to do all we can do, and continue to make Blesta better. Don't be intimidated, if you have something to say, say it! Just make sure you follow the rules.
-
That's the important part of it.. the updates must be verified as being trusted. The default option would likely be not to update automatically, or to update with security patches only. We have discussed this internally at some length, but we have some other more critical features to implement first.
-
I've confirmed the quantity issue and created task CORE-1105 to address this. Bug reports should contain only one item per thread. However, to address your other question, the ability to add coupons to services after they have been created belongs to task CORE-1066 and you can track the issue there. Additionally, there is a price override option for services coming in a future release, per CORE-747 which may be of interest.
-
Is it public? Can you PM me the link? The options are sortable within option groups, not sure why they would appear randomly.. haven't had any other complaints about that as far as I know. The toggling of checkboxes I could see potentially happening if they have the same name as another field. That's where I would look. Happy to take a look at it if you want to send me a link though.
-
Awesome! Maybe we should do error checking on those pesky value fields..
-
It should show all three. Do you have a different value for each item in the drop down? Take a look at this screenshot, it's an example of a drop down for IP addresses which correctly shows 3 items in the drop down.