jquindlen

4.9.36 is out now. Let me know if it fixes your issue when you turn on the new setting. Note that I don’t think it will fix old tickets, so you’ll need to test it on new tickets to see if it works. Please let me know either way, and thanks again for your help and patience!

Alright, I figured out that patch. It will be in the next update, version 4.9.36, out a little later today. You’ll have to switch on the fix from wp-admin > Support Tickets > Settings > General > Force Sync MySQL timezone to PHP timezone? > set to Yes, and save settings.

That’s a known issue that happens when your server is misconfigured with a PHP timezone that does not match your MySQL timezone, causing time based calculations to fail.

This happens in some shared hosting environments where the MySQL server is on a different machine than the web server, but can also happen when both are on the same server but are configured to incorrectly use different timezones. Easiest way to fix that is to change the timezones on one of them to match the other. The easier way is to sync your PHP.INI timezone settings with your MySQL timezone. If that seems like a daunting task you can probably just open a ticket with your hosting company and tell them you need them “to fix the php.ini timezone so that it correctly matches the MySQL timezone.”

I’m working on a more generic fix that should work in all shared hosting environments, but it may not be feasible to implement, nor is it ideal because it will add an additional database query on every page load (to temporarily change the MySQL timezone to match the PHP timezone.) I’m still trying to figure out how I can override WordPress’ $wpdb object because I will have to make sure that this new timezone override is the very first query run after $wpdb makes it’s connection, so if the WordPress core code doesn’t expose a hook directly afterwards, I may not be able to provide any patch at all.

So yeah, very best solution to this problem is to configure the PHP and MySQL timezones to be identical, as they should be. I’m working on the potential $wpdb patch, and I should know soon whether or not I can make the timezone query execute at the proper time or not, so I will update this thread accordingly at that time. Thanks for your help and patience.

For the record, his solution was:

File names should be:
wpsc-support-tickets-el.po
wpsc-support-tickets-el.mo
and not
wpsc-support-tickets-el_GR.po
wpsc-support-tickets-el_GR.mo

Sorry you had a bad experience, but 1) you do not need a static IP address and 2) you do not need a SSL certificate. Just clarifying for anyone else who happens to take a look at this, as I’m not sure why you got that impression.

Do you get any javascript errors on your console?

Sorry it took me so long to see this. Not getting emailed when these topics are created.

Anyway, the common problems that cause shipping calculations to fail are lack of a 5 digit origin zipcode (the zip code you ship from) as well as a lack of one or more packages associated with a product. Let me know if that helps or not!

Since you’re using PRO, I’ve replied to you on the PRO support forums here:
https://indiedevbundle.com/forums/topic/change-languages-create-new-departments/

Fixed. Thank you!

Double check that the shortcode [idbsupporttickets] is in the body of the page of you created.

Yeah, the reason is that if I didn’t remove them then on ticket & reply submission you would have an invalid database query, because \ is an escape character. Allowing \ would also be a security threat since using the escape character would open the door to executing custom queries against your database. You can’t trust users to not hack your database given an opportunity, so no escape characters are allowed in titles or body. Hope that clarifies things for you. Thank you!

Glad to be of assistance!

You can already translate them. An out of date Italian translation already exists. If you want to update it with the latest .POT file I would appreciate your contribution. I’ll push out a new update with the latest translation files. If you’re not sure what I’m talking about, have a read through this:
https://codex.www.ads-software.com/Installing_WordPress_in_Your_Language

And also click on “Translations” in the table of contents for more instructions:
https://indiedevbundle.com/app/idb-ultimate-wordpress-bundle/#idbsupporttickets

Implemented in 4.9.30

Yes, it’s been in the works for awhile. Shooting for Q1 2015.