Paul

In my opinion, Suhosin is terrible and more often than not breaks legitimate applications.

Is the IPN enabled in PayPal? Did the payment originate from Blesta v3? I haven't experienced any of these issues with our installation, except for imported recurring subscriptions, which were set up in v2 after migrating to v3 because of an email address mismatch between our settings and the email PayPal sends in their IPN.. though in this case it does appear in the logs.

If you SSH in as your cron user, are you able to execute mysqldump? I'm not sure what else it could be, might require some debugging.

I wasn't going to say anything until we made an official post, but it's true. They signed over full rights to the cPanel extended module to us. We will be releasing it for free shortly, after we have had a chance to review the code. It is interesting that they reached some kind of deal with those other guys.. I get it, they can expand and eliminate a Blesta module developer at the same time. I have some other theories, but I'll keep them to myself. In any case, I look at it as a good sign of our success.

Hi Barry, Multi-company hasn't been tested with a large number of companies, and isn't intended to be used as a SaaS in the manner that we are licensing it. If you'll have a dozen or two companies, that will probably be alright.. but I would suggest becoming a Blesta reseller and hosting a fresh installation for each of your users. We can do snapshot billing so that you pay monthly for only the number of licenses you have active on the 1st of each month. Cheers

The lock is cleared after 6 hours.. and the task will start to be executed again. As Tyson mentioned, the query in this thread is meant to help identify which tasks are failing and we plan to implement this in the interface so that running the query won't be necessary. Most people don't experience this issue at all, so this tool was fairly low priority, and the lock is self cleared.

I don't think Payflow pro uses an IPN, it's their merchant gateway. If no response from Payflow, it's probably port 443 egress that's the issue. To be safe, I would disable the firewall entirely and test again though.

Thanks for the feedback, we are definitely going to be making some changes to, and adding additional order types and order forms as we go forward.

Linux server? mysqldump binary exist? exec() and system() functions allowed in PHP? mysqldump is executed to create the database dump, and then it's SFTP'd over.. it may be that it's failing before it gets to the that point.

Please advise if this corrects the issue for you.. It's always good to have some confirmation before releasing an official fix.

Thanks for reporting this!

We might have to come up with a policy for how often an advertisement can be posted.

CORE-809 and CORE-813 have been resolved and will be included in the next patch, 3.0.5.

Thank you for the detailed response. I have added a task for the redirect, it should do the redirect whether you pay in the client area, or through the order system. CORE-809 addresses the editable description CORE-813 addresses the redirect issue We will investigate the "Return to" name, I'm not sure how that is set.

Hi Rich, Is that what your accounting software needs to do the import? What software are you using, and can you provide an example of all the fields you require?

I thought we had something scheduled, but nope just a note about late fees cannot be applied to proforma invoices. Do you find it's necessary to have a specific, unique late fee value per package? Some people prefer a late fee to be a fixed amount, a percentage of the invoice total, or interest calculated daily or monthly. We would want any such late fee system to cover at least the most common scenarios.

For 2.5, look in order_forms/register_client/templates/ (If you're using the register order type) and look at step1.pdt and structure.pdt. You will notice the form fields exist here, and you can pre-populate them from your session variables. I'm assuming you were the one I talked to over the phone?

Automation is controlled by setting up a cron, but if you're having issues with email specifically it may be unrelated to the cron. To test, I suggest using the "Email Client" feature under "Account Actions" for a client profile. This will allow you to send an email right away without waiting for any automation tasks to do it. It should allow you to test if PHP Mail or SMTP are working. If you're having trouble with email delivery, specifically SMTP, please post a screenshot of your setting here (And please mask the hostname and password) Also, are you using an SMTP server like Gmail, or Mandrill? Do you have the ports open at your firewall?

Sorry, Scott beat you on that.. hence the pre-designation to CORE-628, however you reinforce the need for such a feature. The sorting would happen under the group, in the expandable area where all member packages are listed.. unless I'm misunderstanding? It's not a sort order for all packages in the system, but rather packages within a group since a package may be assigned to multiple groups and it's sort order in each may be different.

Thanks for the report, can anyone else confirm?

Just a note on this. The reply-to address is always set to the email address defined for the department, and replies should go to the right place. However, I have added a task, CORE-810, to use an email tag in the From Email field for the template. This will effectively set the from email to the support department email.

Blesta strips out content from the reply that is quoted, and the "On Sat... wrote:" text isn't quoted. We may be able to take a look directly above the quoted text for a similarly formatted string, but this may vary from mail client to mail client and a solution may not work across the board. The alternative is that we ask users to "Reply above this line" and remove everything below it. We opted originally not to do that because users may ignore that. Open to suggestions

A setting could work, but I'm not sure how best to implement it. Consider the following cases.. 1. We add an https option for email templates, how do we enforce it? We could do a string replace for http:// and change it to https:// within the template before sending it, but if you add any http links in your templates, they would be converted as well, and this could be a big problem. 2. During install, (or immediately after), we could ask that question, and simply update all email templates to use that schema. This would be a one time conversion and mean that adding http:// links in your templates later work work fine and not be converted. Do you have any suggestions? I understand that manually updating all the email templates can be a pain, and we want to minimize the necessity to do so wherever possible. The only way I can see this working well, is some kind of post-install wizard that asks common questions like this.

Does anything show up in the module log? Tools > Logs > Module. If the email address entered into the gateway in Blesta doesn't match that from which PayPal is including in their IPN call, it won't be credited. Some people have multiple aliases, and we have a task so that these aliases can be added to the gateway and be accepted as well. (CORE-697) I found a task, CORE-662, that resolved an issue with an error being displayed within Blesta when returning from PayPal. This was solved in 3.0.1. However, this may be a matter of the user clicking the return link, which is mentioned in this case, and an automatic redirect. This may require another look. I agree, the user shouldn't be able to edit the item. I have assigned this to CORE-809.

Please understand that all bugs must be confirmed. As we do not currently have an IIS environment, it's difficult for us to do so when they are Windows only related. We also rely, at least partly, on the community to confirm bugs. Different users may experience different things, and a bug may be multi-faceted, requiring a more broad fix. You certainly shouldn't have to maintain your own build, and we don't recommend it. Not all bugs reports are replied to immediately. Bug reports and feature requests are best for the forum. When a ticket is submitted, it's typically reviewed by one person, or escalated to another person. On the forums, it's open to everyone. I'll take a look at some of your other threads.