How to upgrade from 3.5.1 to 3.6.1?
-
We use the latest version of WP.
How should we upgrade to 3.6.1? Will the old events be automatically ported? Why is there no guide in the “INSTALL” section for old time users of this plugin?
I use the
ecp_single_template.phpin my theme. I understand this is now deprecated. Is there anywhere I could go to read how to do the theming now? It’s not linked from the plugin’s wordpress page.Many thanks for any pointers!
-
I just deleted the old plugin, and installed the new one. Fortunately old events show.
But when I create a new event, it does NOT get saved. Even when I publish it. What gives? Where are the events going?
EDIT:
Upon some investigation, it seems the dates of the new events are getting stored in some format that makes them show up at the bottom of the Events Listing in the admin area. Why’s this? Why is “June 14, 2014” older than “March 20, 2012”?In what way is the new plugin saving these events?
Something is wrong, because when we click on the event’s preview link, or its permalink, we get a 404. Other threads related to 404 here seem to be unanswered too. What gives?
This is a fresh install of the plugin!
We use MySQL
Ver 14.14 Distrib 5.6.16, for Linux (x86_64) using EditLine wrapper.Even with the dates being stored in some weird way such that June 2014 is considered older than March 2012, the issue is that the events are NOT showing up on the site at all.
I have five events in june.
This is the events calendar on the site:
http://thearcofluzernecounty.org/events-calendar/What gives?
I enabled the debug option, but the “Debug Bar” plugin does NOT work in WP 3.9.1. And all that this events plugin is writing to the PHP log is the following useless line:
[Fri Jun 13 23:29:58 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:58 am [Fri Jun 13 23:30:05 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:05 am, referer: http://thearcofluzernecounty.org/events-calendar/2014-03/ [Fri Jun 13 23:30:08 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:08 am, referer: http://thearcofluzernecounty.org/events-calendar/2014-02/ [Fri Jun 13 23:30:10 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:10 am [Fri Jun 13 23:30:23 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:23 am, referer: http://thearcofluzernecounty.org/site/wp-admin/post.php?post=443&action=editAnd just to add — the theme file has no “
tribe-events” folder for custom theming. It should all be the default. Changing to default WP twenty-thirteen makes no difference, each event is still 404.THis happens only with the new events created. Old events can still be seen.
Howdy morespinach,
You have been quite thorough in your debugging here! So the issue you are experiencing is not one I have seen before.
I apologize if our documentation was not clear to you. Upgrading our plugin is no more complicated than any other WP plugin. You just click update. Your method of deleting the folder and unzipping the plugin also works though. 🙂
It was wise to disable tribe-events modifications. While likely not necessary it is a good step.
I am glad you tried the Twenty Thirteen theme. However, have you tried also disabling all other plugins. It is possible that one of them is conflicting and preventing new events from being saved. You should try testing for such conflicts if you have not already. With everything disabled, trying creating a new event and seeing if it saves. If not, are you able to save any other post types like a new WP post or page? Our plugin uses the same API they do. Unless there is a conflict like a JS script, it is hard to imagine why you can save those but not Events.
I hope that helps further you down the debugging road. Cheers!
– Brook
Thank you. We disabled all plugins (which was very inconvenient on a live site), and just left Akismet and Events Calendar live.
Created a new event. Strangely, the event was created with the date June 24, but in the Events Listing is showing *below* much older events from 2012…it should be on top as its the most recent event!
Anyway, click on “View Event” shows 404 still. Why?
Debug option is not helping. In the Apache log, it just adds that silly un-informative line:
[Fri Jun 13 23:29:58 2014] [error] [client ...] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:58 amWhat does this tell me?
Much appreciate any other pointers! Thanks
If it is possible, I don’t mind sharing WP-ADMIN access with you as this is having us root our hair out. We have absolutely no idea where the problem may be. Thanks!
One thing. My theme doesn’t have
functions.phpat all. We don’t need it. Is this an issue? Just FYI, the default WP theme also does not work so I doubt this is an issue, but just mentioning it.Howdy morespinach,
The lack of a functions.php is no problem. In fact, as a reul of thumb that makes the theme even more compatible with a variety of plugilns including ours.
Your server is generating 404 and 500 errors, predominantly when linking to /site/cache/*. I am not sure if it has server side caching or something. But, either way that seem the caching is at least causing some problems.
Thank you for trying those debugging steps. I realize that it is a pain on a live site. There is good reason why many high-traffic sites have staging and live servers. That way they can test for stuff like this without affecting their live server. Definitely best practice and recommended industry wide, even for low traffic sites when possible. But, understandably not everyone can afford this capability, and so they instead have to test on live sites and just accept the enormous risk of data corruption.
Just so you know our free support is limited to general guidelines like the above. If we are unable to replicate your issue on any of our testing environments, which I am not, then this boils down to something unique to your server and site. I definitely can not log into your site to further assist. I know you do not want to hear this, but I hope you understand. Our free support is just targeting bugs in the plugin and general advice. If we offered PRO support for free then Tribe would not be able to afford employees like me, and the plugin would quickly die.
Cheers!
– Brook
Thanks Brook. Where did you find the linkages to
/site/cache/?Our “Media” links are customized. We use a CDN and anything stored in the
/site/cachefolder uses thecache.oursite.comURLs. Here is a screenshot of the Media section: http://i.imgur.com/BOnp6W3.pngOther than this, that URL should not be relevant at all. Is the Events Calendar plugin designed to upload some media? Even for a default basic event entry where I haven’t uploaded any image at all?
I am not sure why this should matter at all, and why this is giving 404. The usual image upload is working perfectly fine! What is the Events Calendar plugin trying to do?
Not sure I understand this. This is the plugin support site.
Your plugin does NOT work when all plugins are disabled and the theme is default, while ONLY your plugin is active. It used to work with pre-3.5 version of your plugin before.
Everything else in this blog works fine. The media uploads well. (And when other plugins were active, all of them work fine too. I’ve just disabled them to isolate problems related to your plugin.)
In this scenario, when ONLY your plugin is active with the default theme, and it does NOT work, do I still need “pro” support? What’s the point of your plugin then?
I’m happy to share an admin user ID with you so you can check. Will that help?
Howdy again!
morespinach, I found those links in the source, and in the browser console.
The plugin does not work out of the box with the caching configuration you have. Based on what you are saying it sounds like the caching is server side. We work very hard to make the plugin broadly compatible with countless server environments. However, in our large variety of testing environments the plugin is functioning proper, no one has seen this issue before. It is thus a fairly unique config, hence why it is not something we can support for free. If you want more assistance with this you might be interested in PRO support forums, which is monitored multiple times a day rather than once a week. Obviously that requires a license though.
I want to be 100% upfront of course, and in that vein I want to mention that even with PRO support it is possible that the plugin can not easily be made to work with your caching solution. PRO support will give you advice and the benefit of knowledgeable research into your problem, but even still sometimes problems can not fully be solved via forums due to the instructions requiring a certain level of knowledge from you. If you are somewhat knowledgeable about caching configs then you should be fine. If you are instead fully versed in caching you might try to use your browser console and knowledge to track down those 404s. Find out where they are being generated, and resolve them. If you are not, you might even want to hire someone who is instead of going for PRO support, that way you have an absolute guarantee it will be resolved.
I wish I had better news. I hope you find a good solution. Cheers!
– Brook
It is NOT a caching issue. I disabled all plugins and flushed all caches in all browsers. I also cleared the permalinks, even disabled permalinks, and worked with just the default theme in WordPress.
The events are simply NOT working.
Get used to the idea. There are plenty of other 404 threads, so I hope at some point you’ll realize that this lazy “it is your cache” solution is NOT working. There is some issue in your plugin. It was working for three years, but is NOT working now.
Make it work without caching plugin. I will figure caching out later.
Hi there morespinach. Just wanted to follow-up here – I realize you’ve moved on to another plugin by now, but I thank you for taking the time to try and help us get better. As I noted in the other thread you were participating in (http://wordpress.org/support/topic/page-not-found-error-all-or-a-sudden?replies=18#post-5779580), this actually doesn’t appear to be the byproduct of a problem with our codebase…one of the two issues reported in that other link is almost certainly the cause of the problem here. While I can see how it’d be tempting to view the presence of multiple 404 threads as a sign that there’s a problem in the codebase, I’d caution against doing that based on the information presented in that other thread: the reality is that there are a number of causes that all rear their heads as 404s, and can create confusion among users who might mistakenly think those are all caused by the same source issue (when in fact they’re not).
We always encourage folks to use caching plugins as it is generally a good practice for web development. I wish you the best of luck in finding a different calendar plugin that better meets your needs! Thanks again for the report and apologies our plugin didn’t work out for you.
Caching is not the issue. All plugins were disabled, and theme changed to default, even permalinks removed. Still 404.
Yes I’ve moved on to another plugin. Doesn’t look as pretty, but at least works.
I appreciate the follow-up, morespinach! I’m glad that ultimately, you were able to find a plugin that met your needs. We’ll continue to try and advise users on the best approach for these 404 problems when those rear their heads.
- The topic ‘How to upgrade from 3.5.1 to 3.6.1?’ is closed to new replies.
