Forum Replies Created
-
Posts
-
The number of 404 errors continues to grow exponentially. GWT is sending me messages daily. I deactivated Event Calendar and Event Calendar Pro. I’m hopeful that will clean up the giant mess that was created.
I viewed the source of days with and without events. The days without an event have the code:
<meta name=”robots” content=”noindex,follow” />
Why is Google reporting large numbers of 404 errors if the days without an event have a noindex?
Best,
ChristopherI noticed that the Event Pro demo will display days with no events scheduled and also includes Previous Day and Next Day links that are also days with no events scheduled. How do you keep Google from walking decades of empty days? This seems to be the source of my GWT error messages as Google visits thousands of days with no events scheduled.
See http://wpshindig.com/events/2014-01-30/Best,
ChristopherI visited Settings->Permalinks but that did not seem to help.
In the day view, what should Previous Day and Next Day point to if there is no event scheduled on those days? Should the links not be displayed? Or, should the links point back to some other view that actually exists?
Best,
ChristopherMost of the 404 are of the form http://www.freelapusa.com/events/2003-02-25/
Barry, that is correct. I’ve been using the Redirections plugin successfully for a while, but I had never noticed there are two lists, one is called Redirections (created manually) and the other is called Modified Posts (created automatically). Once I found the tab to open the Modified Posts, it was easy to click on and delete the redirections for the events and venues that no longer existed. The comments in this thread will make sense for anyone who stumbles onto this problem. I’m guessing both Event Calendar Pro and Redirections play nice together as long as you don’t accidentally create extra redirects like I did. And if you do, it’s a simple task to find and delete them. Thanks for the follow up. This is my second day with Event Calendar Pro and I’m loving it.
Best,
ChristopherI was able to find and fix the error. This may help others in the future so I’ll document the problem here. When I created an event with a duplicate name, the slug was event/xxx-2. I’m using the plugin Redirections and this automatically created a redirection from event/xxx-2 to venue/xxx-2. When I deleted both the original and duplicate events, it left the redirection. I went to Redirections/Modules and deleted the bogus redirections and that resolved the problem.
Best,
ChristopherI did not roll back but decided to wait a day a see if this got resolved quickly. When 3.3.1 was available, I updated the plugin and the ending date issue seems to have been resolved. Thanks.
I’ll try and move everything to a sandbox and see if I can recreate the problem. The problem seems to be related to an event that was entered twice with the same name. That created a slugs of the form xxx and xxx-2. I’ve tried deleting all events and venues, but for some reason the system still remembers something about the xxx-2. Does that give you any ideas what might be wrong?
Also, I’m using the plugin Redirections. Do you know if that plugin can be deactived and then reactivated without deleting all the redirection entries?
Best,
Christopher
