Paul

Are you certain they are not in use? By "in use" I mean any service is using the pricing id, regardless of the status of the service (Active, pending, cancelled, etc).

Oh just to add.. for imported packages, from 2.5 or in cases where you need to delete pricing that's in use.. I suggest marking the package as inactive or restricted and adding a new package instead. Until CORE-1041 is resolved anyway.

Pricing that is in use can't be deleted because it will cause problems. Najahost mentioned a soft delete for pricing, this is planned as part of CORE-1041 It's not likely it will be in 4.0 at this point, but it's a high priority item for me.

That's great. Having to hit refresh during development is annoying. I don't have any big reasons why someone deciding between Jekyll and Hugo shouldn't choose Jekyll. Hugo wasn't a complete walk in the park. In terms of creating your own theme in Hugo, there is much left to be desired in their documentation and I had to figure some of it out with trial & error, and look to their forums. In that sense, Jekyll may be more mature. Still, Hugo is very fast and I like the file hierarchy, it's pretty logical.

I was deciding between Hugo and Jekyll. Jekyll is more popular, but Hugo is gaining in popularity. I looked at both and was drawn more to Hugo, partly because Hugo is so much faster in terms of building the site with around ~1ms write time per page. The entire site is written in about 700ms and ready for deployment. I do also like that Hugo's built in server automatically refreshes the site when you save changes, though I'm not sure if Jekyll does this or not.

If Blesta is sending the ticket bounce email template, chances are that the piped in TO email address isn't matching the email address set for the department. What email address are you using for the department, the alias or the actual mailbox?

Piping is instant. You can forward email to another domain that accepts mail on your server and use piping instead.

Thanks, much appreciated! Now we just need to get v4 beta out to ya, and that'll round things out nicely.

The import from Wordpress was useful in that it converted all of our posts into Markdown files that I was able to import into the project. The posts required some tweaking to work properly, but the import saved a ton of time. We built the theme using Bootstrap, SASS, and Gulp, and converted it into a Hugo theme. So, most of the work was building the new site, creating the Hugo theme. Importing Wordpress posts was really the easiest part. I did have to create some shortcodes for displaying Vimeo videos in posts, responsive images, and buttons. They include some shortcodes already, like code highlighting that was very useful. So, posts consist of largely markdown content, and some shortcodes to avoid the use of HTML in the post content.

Thank you for your canadian cents, lol. They end up in our vending machines. No really, appreciate the feedback. Smaller quicker releases is our goal. v4.0 is turning out to be our biggest release since 3.0. Much of it was unavoidable with the framework upgrade. So, hoping to avoid that going forward. In terms of custom code, modules/plugins/gateways, with few exceptions, they should work. One change that you will probably want to make, is to update the buttons to use bootstrap buttons. However, that is largely cosmetic. We built a bridge for backwards compatibility with minPHP 1.0. Still, any custom extensions should be tested prior to an upgrade. Feedback during the beta will be helpful as well.

The feed includes anything we post on our blog. You can change it if you want. For example, if you just want stuff from News you can use: https://www.blesta.com/categories/news/feed.xml If you want stuff from Security, you can use: https://www.blesta.com/categories/security/feed.xml Removing the existing feed and adding those 2 will get you pretty much just information about Blesta.

I have corrected these. They seem to have to do with people that uploaded their own avatar. Seems IPBoard does not reference them with a relative path, and includes http:// in the image tag. I'm sure there are more, if you find any please let us know!

Alright, got Gravatars turned back on. Fixed a couple custom avatars that were hard linking to http:// and causing SSL errors. If you find anyone whos avatar is breaking SSL, please PM me their username and I'll correct it. So, what does everything think of the upgraded forums?

You like it? Some stuff to fix/figure out like why I don't have an avatar. Glad icon is still here.

The forums have been upgraded. One thing to note is that you need to log in with your Display Name. On the old version, it was possible to have a username that was different than your display name. If you are having trouble logging in, login with your name as it appeared when you posted.

Is there any record of it under Tools > Logs > Gateway log? Click a row to expand and show raw input/output. Was the subscription set up within Blesta? Did you move Blesta to a new location after the subscription was set up? I suggest checking your HTTP logs to see what URL the IPN is calling to, if it's making a call at all. This will be helpful in debugging the issue.

See my reply to your post in the other thread here - http://www.blesta.com/forums/index.php?/topic/7061-release-362-security-advisory/?p=45203 You should enable debugging and error reporting and see what the error actually says.

What does the error say? If it is generic, you can edit /config/blesta.php and set this back to true: Configure::set("System.debug"), true); Then you should get a stack trace with more information about the issue. The more information you can provide the better.

The patch includes items from the 3.6.1 patch as well. You can run a diff between the two patches if you want to know what must be overwritten to go from 3.6.1 to 3.6.2 Our patches are meant to be applied to any specific minor version, ie 3.6.0 or 3.6.1 in this case. There are 3 tasks for 3.6.1, however only the one related to path disclosure is public, in coordination with our competition. You may have noticed they released a patch at the same exact time.

You are very welcome. Thanks for patching and letting us know all went through well! For anyone reading this, be sure to run /admin/upgrade, it will write a new config option to your /config/blesta.php config file.

Previous balance is stored statically for invoices and contain the previous balance at the time of invoice generation, this could potentially be used within the PDF template. This field is called "previous_due". Look at other tags in the template like date_billed, date_due, note_public, etc to see how to implement. On the actual emali template, it's called previous_due as well and you can use the tag {invoice.previous_due} in Invoice Delivery (Paid) and Invoice Delivery (Unpaid) This balance of course, does not include the total of the current invoice. So, you'll need to do some math with "total" to get that if you need it.

Very good! Use something like kdiff to compare your custom template and the one included with Blesta. Then you can try to manually merge your changes in and get terms working again.

The "Terms" section content is pulled from Settings > Company > Billing/Payment > Invoice Customization. Specifically the "Terms" box in the "Look and Feel" section. This is a company-wide setting. It should be the same for all clients within that company. Unless, perhaps, a manual database change was made to create this setting for affected client groups. This cannot be done in the UI, but probably could be done manually in MySQL.

Version 3.6.2 is now available. More information on this advisory and direct download links can be found at http://www.blesta.com/2016/08/02/security-advisory/

May be a UTC date issue depending on your time zone. I think we made some changes to Billing Overview widget recently.