Upgrade causes event path issues

[Sheila]

I’ve been a long time user of this calendar for clients. This particular client is a non-profit and they’ve avoided paying for the upgrade for way too long. I finally told them they couldn’t leave such an old plug-in live as it was a vulnerability. I made a clone of the site, then I upgraded from v2.0.11 to v3.6.1. That’s a HUGE update! The calendar comes up perfectly. HOWEVER, the single event pages do not. Bottom line is that there’s something amiss with the links.

Live site calendar:
http://sococulture.org/calendar/
http://sococulture.org/events/am-beyond-ancestrycom-searching-for-your-ancestors-online-muckleshoot-library/

Cloned site with update:
http://sococulture.wpstagecoach.com/calendar/
http://sococulture.wpstagecoach.com/events/am-beyond-ancestrycom-searching-for-your-ancestors-online-muckleshoot-library/

As you can see the single event page works on the live site and not on the updated site. It’s the same path. It should work. I have made sure there are no caches on and I’ve re-saved permalinks. They’re the same theme and plug-ins (a clone) so it should all work the same in both cases. But because I know the routine, I have changed the theme to 2014 and get the same result. Then I also deactivated ALL plug-ins except EC & ECP. Still same result.

One of the reasons it seems to me it’s about the paths is that when you click on an event on the calendar it always times out. But if I copy the link and remove the date at the end the page actually does come up. Its adds the date back on but it will resolve. Try Mary Olson on Saturday June 21. Link doesn’t work (none of them do). I just want the events to resolve when clicked on from the calendar. Something is funky here.

Another symptom is that even when I successfully get a page to load by dropping the date, the next and previous events links also don’t work. If you can get to this page you’ll see http://sococulture.wpstagecoach.com/events/mary-olson-farm-open-hours/2014-06-21/ (and if you can’t, try it again w/o the date)

I will post an admin login privately. thanks.

[Sheila]

This reply is private.

[Casey]

sheilahoff,
Thanks for getting in touch and sorry to hear you’re having trouble here, but hopefully I can help. Can you visit the Permalink Settings page, confirm everything there is correct and hit update? That might help to refresh to rewrite rules table. With that done, see if the page is accessible as expected.

Thanks! 🙂

-Casey-

[Sheila]

Casey….I psted originally ” I have made sure there are no caches on and I’ve re-saved permalinks. They’re the same theme and plug-ins (a clone) so it should all work the same in both cases. But because I know the routine, I have changed the theme to 2014 and get the same result. Then I also deactivated ALL plug-ins except EC & ECP. Still same result.”

But just in case I tried saving permalinks AGAIN. Still no joy. Please log in and take a look. thanks.

[Casey]

sheilahoff,
Are these sites both hosted on the same server? It’s possible that even though you’re using the same theme and plugins, you might still experience issues because of a different server configuration.

In this case, I suspect that there is something peculiar going on with your .htaccess file. Can you verify that the file exists in the root of your WordPress directory and is writable?

[Sheila]

No….they’re not. I made the clone using the new plug-in WPStageCoach so the clone is on their server. On my live site the htaccess is NOT writeable actually for security. On the cloned site it is writeable. I’ve pasted what’s in the clone site htaccess that is not in the live site below.

Question though….if we find that the issue is the environment on the clone site, and I go ahead and update on the live site…what happens if it’s STILL like this on the live site? I won’t have a good way to easily revert and their live site will be a mess!

####WP Stagecoach .htaccess file ####
#### This file will NOT be transferred back to your live site if you make changes in it ####
#### Lines that start with #WPSC# have been commented out to ensure no errors with your staging site while running on our servers. ####
# Begin WP Stagecoach redirects
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*\.jpg$|.*\.jpeg$|.*\.png$|.*\.gif$|.*\.svg$|.*\.bmp$|.*\.tif$|.*\.tiff$|.*\.pct$|.*\.pdf$|.*\.git$|.*\.mp3$|\.m4a$|.*\.mp4$|.*\.aac$|.*\.aif$|.*\.mov$|.*\.qt$|.*\.mpg$|.*\.mpeg$|.*\.wmv$|.*\.mkv$|.*\.avi$|.*\.mpa$|.*\.ra$|.*\.rm$|.*\.swf$|.*\.avi$|.*\.mpg$|.*\.mpeg$|\.flv$|\.swf$|.*\.gz$|.*\.sql$|.*\.tar$|.*\.log$|.*\.db$|.*\.dat$|.*\.123$|.*\.zip$|.*\.rar$|.*\.iso$|.*\.vcd$|.*\.toast$|.*\.bin$|.*\.hqx$|.*\.sit$|.*\.bak$|.*\.old$|.*\.psd$|.*\.psp$|.*\.ps$|.*\.ai$|.*\.rtf$|.*\.wps$|.*\.wpd$|.*\.dll$|.*\.exe$|.*\.wks$|.*\.msg$|.*\.mdb$|.*\.xls$|.*\.doc$|.*\.ppt$|.*\.xlsx$|.*\.docx$|.*\.pptx$|.*\.core$|^core.*)$ http://sococulture.org/$1 [R=301,L,NC]

# End WP Stagecoach redirects

[Casey]

Shiela,
Great question! I definitely wouldn’t recommend going live when you’re unsure what will happen in production. When creating a staging site, I typically create a subdomain on the same server (or use a different account with the same host). This ensures that the server configuration I’m testing with is identical to my live environment, and will give me the most accurate testing results before going live.

I would give that a try and see if you’re still experiencing this permalinks issues.

[Sheila]

yes, well, this plugin is much more convenient and has worked for several other sites. I can setup a sub-domain to test I guess. But it’s a PITA compared to using WP StageCoach.

What can you tell me, if anything, about the htaccess? Why did you say it needed to be writable? Do the things they added to it tell you anything? I’ve emailed them for input as well.

[Casey]

Sheila,
I’m not seeing any of the standard WordPress permalink rules in that .htaccess file, which might be part of the issue. The core issue is that our plugin dynamically adds rewrite rules to WordPress, which for some reason aren’t being applied on your staging site.

Finally, I also noticed that WP StageCoach is still in an alpha stage, with several known bugs, some of which might contribute to this problem.

Hopefully that helps to answer your questions. Thanks! 🙂

-Casey-

[Sheila]

Yes I know it’s in alpha. I’ve emailed Jonathan. I’ve also just cleaned out the rest of the htaccess file. I hadn’t sent you all of it. But are you saying that ECP won’t work on a site with a locked htaccess file? Can I unlock it, install and then relock or it can never be locked? I host 35+ WP sites on a dedicated server. I worked with a security pro because we were having issues with brute force attacks. So one of the many things he had me do was lock them all.

[Sheila]

The plot thickens. I’ve made a sub-domain on the same server and tried to update both the free and Pro plug-ins. Now I’m getting a huge Fatal Error plug-in cannot be activated in the dashboard. I don’t even know how to interpret all this info! Site is now at http://www.tribe.hoffmangraphics.com but plug-ins are not currently able to be active.

Warning: require_once(/home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php) [function.require-once]: failed to open stream: No such file or directory in /home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 164

Fatal error: require_once() [function.require]: Failed opening required ‘/home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php:/home/hoffman/php’) in /home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 164
Fatal Error
The site encountered a problem that it cannot recover from. Please use the following information to try to resolve the problem.
Error Message

Fatal Error: require_once() [function.require]: Failed opening required ‘/home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php:/home/hoffman/php’) in /home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 164

Description
The The Events Calendar plugin code created an error that caused PHP execution to fail.

A required file (/home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php) was unable to be loaded since it does not exist. This error typically indicates that the code has a typo (require_once(‘hom.php’) rather than require_once(‘home.php’)) or that the file is actually missing. Try uploading the plugin again to see if that fixes the problem.
Solutions
Invalid code modifications can cause this problem. If you have made any modifications to the plugin, remove them and try to load the site again.
It is possible that this plugin’s code is out of date and that an upgrade is available. Check with the plugin’s author to see if an upgrade is available.
There may be a conflict with another plugin running on the site. Try upgrading the other plugins on the site. A plugin conflict can be ruled out by deactivating all the other active plugins on the site and checking to see if the error still occurs.
The The Events Calendar plugin may not have been fully uploaded. Uploading the plugin again could fix the issue. Important: If you do this, you will lose any modifications made to the plugin.

Error Source Details
Type Plugin
Name The Events Calendar
Version 3.6.1
Author Modern Tribe, Inc.
Path /home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar
File lib/the-events-calendar.class.php
Other Software Details
WordPress Version 3.9.1
PHP Version 5.3.28
Full Error Details
Type Zend Compile-Time Error (E_COMPILE_ERROR)
Message require_once() [function.require]: Failed opening required ‘/home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php:/home/hoffman/php’)
File /home/hoffman/public_html/tribe/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php
Line 164
Type Description This type of error indicates that the PHP code is violating a restriction enforced by PHP. An example of such a violation is trying to use a reserved word for a class or function name.

Note that this message is generated by iThemes.com products when an error is encountered on the site. While an iThemes product is generating this message, it is not necessarily the cause of the problem.

[Sheila]

PS…I unlocked the htaccess but that did not fix this.

[Sheila]

PPS…I just cleared the APC cache and I’m now able to activate. Will report back about how it works. Sorry for alarm.

[Sheila]

OK…I now have the updated plug-ins activated on the same server as the original site and I have made sure htaccess is unlocked AND I have reset permalinks. I still have the exact same problem as before.

I have created an admin user with same credentials as on previous install (see private above).

[Casey]

Sheila,
I deactivated all other plugins and switched to the default 2013 theme, and now the events are displaying correctly with no 404 errors: http://tribe.hoffmangraphics.com/events/pm-time-travel-rainier-youth-choirs-season-finale-concert/ This leads me to believe that there’s something conflicting with either your theme or plugins that is the culprit.

Sorry for the inconvenience, but hopefully this helps you to troubleshoot the issue further. Thanks! 🙂

-Casey-

[Author]

Posts