Home › Forums › Calendar Products › Events Calendar PRO › Agree – latest update made WPML worse not better
- This topic has 12 replies, 2 voices, and was last updated 8 years, 9 months ago by
Lorraine.
-
AuthorPosts
-
June 2, 2017 at 8:10 am #1292368
Lorraine
ParticipantEvents are not showing at all on my second language pages, and the calendars (as mentioned here) no longer ‘stick’ to the correct language. It is a bit of a disaster to be honest.
Unfortunately due to a problem with WPML itself I wasn’t able to back up and test this release as the tables are too big to write to my test server. So I took a chance and updated the live site in the hope of getting the promised improvements. Aaarrgghhh!
========================
PLEASE LEAVE FOR SUPPORT
Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/month-view-navigation-prevnext-doesnt-stick-to-language-wpml-2/June 6, 2017 at 12:28 pm #1293962Andras
KeymasterHi Lorraine,
Thanks for going Pro and welcome to the forums! I’m really sorry you are having this issue as well with WPML. We are aware of that issue and our developers are working on a fix. It is already on high priority.
Unfortunately at the moment there is no known workaround for this. We ask for your patience.
Thanks for your understanding!
Cheers,
AndrasJune 14, 2017 at 2:19 am #1297679Lorraine
ParticipantIs there any way I can go backwards with versions so that it works again?
This is a real problem for me / my client.June 14, 2017 at 5:45 am #1297739Andras
KeymasterYou can try to roll back The Events Calendar on your site to version 4.3.5, and to roll back Events Calendar Pro on your site to 4.3.4. These versions are the most stable to work with WPML. Though at the moment I’m not sure whether this issue is present in that version or not, I’m sorry.
Andras
June 22, 2017 at 4:05 am #1301608Lorraine
ParticipantI have just upgraded to the latest releases and the problem appears to be fixed.
I wish, though, that your support system would notify us of likely fixes. Before doing the update I had made full preparations to revert to earlier versions and had also downloaded the beta releases ready to test those.
You could have saved me a LOT Of time by updating the ticket!
This complaint is NOT aimed at the individuals that are working the tickets, it is aimed at whoever is responsible for your processes, systems and procedures. It’s not the first time that my life has been made more difficult by the way you do things e.g. the way you do licensing for multilingual sites is not fit for purpose!June 22, 2017 at 2:26 pm #1301959Andras
KeymasterHello Lorraine,
I’m really sorry for your troubles!
I wasn’t aware of any fix going out for this, and the bugticket I am monitoring for your issue still hasn’t been resolved. So I’m not quite sure what has happened here, but I’m happy to hear that your issue got solved.
Thank you for taking the time to share your honest feedback with me. I understand your frustration, especially the one coming from this issue.
Normally our bug-fixing process goes like this:
- user reports bug
- we test it
- if we can reproduce, then internal bugticket is created
- user is notified of this and thread is set to pending fix
- if more users report it or it’s a usability issue, then ticket gets higher priority
- developer gets assigned and does the fix at a point
- fix goes through an in-depth QA process to make sure we don’t release a fix until we feel like it is fixing the issue 100% and is not creating 2 more bugs
- fix is released
- user is notified of the release
I understand if you would like to be notified of status changes. Unfortunately we don’t have a system in place yet for this. However, the user – like yourself – has the chance to ask for the status of a ticket any time in the thread, and we’re happy to provide a status update.
Since your issue seems resolved would you be OK if I closed this ticket? Or do you have any more questions related to this topic I could answer for you?
Thanks,
AndrasJune 22, 2017 at 3:44 pm #1301999Lorraine
ParticipantAt this point it’s even more crazy since something that 100% definitely
WAS fixed earlier is now broken again. I will test this again tomorrow
since the only thing that is likely to have changed is that the wpml
table that collects cached object pages for string translations (I will
need to look that up) was emptied and is probably starting to fill
again. This might give a clue as to the issue if that’s the case…June 23, 2017 at 11:13 am #1302431Andras
KeymasterHi Lorraine,
I’m sorry to hear about your troubles. Please do let me know what you find and if there is any way I can support you.
Best,
AndrasJune 23, 2017 at 1:40 pm #1302500Lorraine
ParticipantThis reply is private.
June 23, 2017 at 1:42 pm #1302502Lorraine
ParticipantThis reply is private.
June 23, 2017 at 1:50 pm #1302509Andras
KeymasterThis reply is private.
July 15, 2017 at 9:35 am #1321720Support Droid
KeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘Agree – latest update made WPML worse not better’ is closed to new replies.
