Ending Hours And Category Removal?

[grupoakro]

Hi!

I just noticed all of my events ending at 0:00 although they have correctly setup the ending time in their setup.

Also, I’m unable to see the Spanish translation for “Event:” and for “Category:” though every other word are correctly translated. I’ve managed to change “Event:” directly within the single.php file, but I’m unable to find where to change “Category:”…

Any ideas?? Thanx!!

[Rob]

Hey grupoakro. The end time issue should be fixed for most users with the 2.0.4 update (please make sure you’re running 2.0.4 for both free & PRO), in instances except those where users are running UTC time. Is that possibly the case for your site? Let me know.

As for the translation issue; I believe if I understand the problem correctly, this is a bug we’re aware of and have patched in the 2.1 code. If you wanted to send an email to pro /a/ tri.be with a link to this thread, I can get you the new code to test with (so we can see if it fixes your issue).

[grupoakro]

Hi Rob!

I’m running 2.04 Pro, yep, bit I don’t know what do you mean with UTC time…

Regarding to the translation, I’d be most grateful if you send me the code to get it tested.

Thanks!

[Rob]

Hey grupoakro. Thanks for the follow-up; on the time zone front, I was curious as to what your settings there were. Mind posting a screenshot of your time zone settings?

Email pro /a/ tri.be with a link to this thread and we can get you the translation code.

[grupoakro]

Hi!

Just sent the email for the translation file.

My time zone settings are set on UTC+1, in j F, Y format.

[Rob]

Sent it over earlier. Let me know how the testing goes.

[grupoakro]

Hi Rob!

Unfortunately it didn’t do the trick. Keeps on showing 0:00 as the ending time for every event in the calendar view. On the single event view, it does show the correct ending time, BUT it does show “Event” and “Category” instead of the correct translation in Spanish.

[Rob]

Thanks for confirming, grupoakro. Bummer to hear that didn’t do the trick. At this point the best suggestion I’ve got would be to wait until the official 2.0.5 release, which is on track to be out within a week or two. Addressing the UTC time zone problem is a priority for that release so the fix should be deployed there.

Apologies I couldn’t offer up more in the short-term. If upon installing the official 2.0.5 code when it’s released, you find the issue persisting, please let us know and we’ll do what we can to rectify it with haste. And let me know what else I can do in the interim.

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts