Paul

It looks like there may be 2 usernames that are the same. Since usernames must be unique, you're bumping into this error. Cody can probably provide more information about how to fix such a case, but if you're able to find and correct any duplicate usernames in v2.5 prior to doing an import (And make sure that no users were added in v3 that also exist in 2.5) you may be able to get around this issue.

You got it! Having restricted packages be set on a per client group basis might be a good feature request.

It is a neat feature, though it annoys me in some cases. I wonder if this would be a good feature request for a poll.

Blesta 2.5 doesn't have recurring invoices, so no recurring invoices could be imported into v3. Or do you mean services? Every time you attempt to do an import, you should be doing it on a fresh install (ie no clients, services, packages, etc). If you need to, do a fresh install of v3 in the same location you have it, and then make a backup of the database so that you can just restore it if you have to run the import again. If your next import doesn't get everything after a fresh install you can do some debugging.. Then, let us know what, if any errors are displayed. Also, make sure you're following the steps listed here http://docs.blesta.com/display/user/Migrating+to+Blesta to migrate from 2.5 to 3.0.

The import is very complete, it just doesn't import ticket attachments. You could copy those over if needed, but most people don't. The AES key is not actually stored in Blesta v3 anywhere, the key is needed so that the CC details, and possibly other encrypted values can be decrypted. They are then re-encrypted and stored in v3 using a different cipher and a different key.

You can change the standard number of items that appear per page in the config/blesta.php config file.. Configure::set("Blesta.results_per_page", 20); This applies to everything that is paginated though. We have plans to add a filter option at the top of most of these kinds of listings. It will be very useful for tickets, and could be useful here for packages as well, and allow you to change the default items per page, and save it for your staff member. We'll have to discuss. The problem here is that a single package could be a member of many groups, or it could be a member of no groups. If viewing Groups, you can click the group name to show all member packages within that group. Does this allow you to find the appropriate package that may have a similar name?

What are the default settings, and what did you change them to? Interesting that it tossed an internal server error, and not something more descriptive.

Just to add to that, I would rename the directory used for 2.5, and then recreate it for 3.0. You don't want to have 3.0 files in the same place as 2.5 files.

lol, curling. I do find curling entertaining,.. it might be the only thing I watched during the last olympics. SWEEP FASTER!

I've been to a couple Duck games at the Honda Center (I still prefer to call it The Pond). Hockey is pretty entertaining to watch.

Attached are the 2 files committed after plesk_customer_accounts.php. - plesk.php (~93KB) goes in /components/modules/plesk/plesk.php - plesk.php (~8KB) goes in /components/modules/plesk/language/en_us/plesk.php Be sure you put the right plesk.php in the right place. plesk.php plesk.php

I think what Tyson did here he did after posting the hotfix above. If I'm right, the issue you experienced with changing the renewal date is already corrected it's just not in the file you downloaded. Tyson, can you confirm? I can post a new file for testing if that's the case.

Can you let us know the Plesk version? Tyson is investigating this right now.

yep, patched. closing thread

Just a quick announcement to any Blesta customers who also have WHMCS installs. You should take them down immediately until a patch is released. Please see http://www.webhostingtalk.com/showthread.php?t=1309491 I'm not going to post a link to the POC, however you should know that it is a CRITICAL vulnerability.

Your suspend error may be the result of the username not existing, make sure the username is set in the local edit.

What version of Blesta are you running? It sounds like it may be 2.5.. if so, then there are no module options on edit and you'll want to make your changes under local edit. To cancel, simply set a date for the canceled field.

This is only necessary when you add the service as an admin to a client's profile. If you cancel, suspend, or edit the service through the "Active" link you will see a "Use Module" check box. Uncheck this box when performing an operation to prevent it from calling the module. You want to uncheck this whenever you don't want what you're doing to make an API call to your WHM server and affect the cPanel account there. For the duplicate, click the "Active" link and cancel it, but uncheck the "Use Module" box when doing so. If adding it to Blesta when it already exists in WHM, just make sure to uncheck the "Use Module" option when adding. If you want to link it to your WHM server for account suspensions if they don't pay on time, then click the Active link, and input the actual username in the username section and uncheck the "Use Module" option and save. You are very welcome!

What do you guys think, a pop up window with an HTML invoice and an option there to download the PDF version? Or embed the invoice in the page in the client area?

Check your email templates, it may be that it's using https:// for the link in that email when you don't have SSL set up for the domain. Regarding the other error about connecting to the remote server for the module, uncheck the "use module" option to update Blesta without connecting to the cPanel server. If you add a cPanel hosting account to Blesta that's already set up, then you'll want to uncheck the "use module" option at that time as well. After it's added, click to Manage the service, and make sure the proper username is entered for the username field. This will link it to the server so suspensions and unsuspensions can happen automatically. If you try to remove the service from Blesta and don't want it to delete in on your WHM server, always be sure to uncheck the "use module" option.

That's correct. Custom payment types.

We don't make the pricing public. Did you email from the same address you signed up from the forums with? Do you currently have a Blesta license? VAR accounts are unlimited licenses on servers you own or operate for a flat monthly fee. Most customers are better suited for the standard reseller plan, which has a much lower commitment.

Not happening anymore? I remember before you said you had 2 windows open logged into each company watching the ticket queues and it worked great. For me, it looks like the other company but it loads the ticket queue for the last company you switch to. This can give the appearance that it's the ticket queue for company A, but it's actually the ticket queue for company B. Make sense? I just wonder if that's what's happening here.

IPBoard does that, I think it's to prevent yelling in titles, but It is pretty annoying since it forces Cpanel instead of cPanel, Cdt instead of CDT, etc.

Yeah, this would be pricing in a single package. Duplicate terms with different prices. I'm not sure it will solve anything in Dave's case, but I thought I'd throw that out there since this functionality is probably not common knowledge.