• Resolved Chad Honea

    (@chad-honea)


    Posted this yesterday on the Pods site, but no reply yet. So I’m posting here. Kind of in a bind and I’m stumped.

    Updated to WP 3.7.1 from (IIRC) 3.6.1 and included a Pods update to 2.3.18. Now suddenly all Pods pages are 404, but the Pods are still there in the back end. Any ideas of where I should start looking?

    All pages are still marked public and published. I think I’ve run through the obvious stuff, disabled all plugins, etc.

    Any help would be appreciated!

    http://wordpress.org/plugins/pods/

Viewing 15 replies - 1 through 15 (of 24 total)
  • Did you try to update your permalinks settings after update?: Settings – Permalinks – Save Changes.
    You could also try: Pods Admin – Settings – Clear Pods Cache.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Are you using the ‘Associated Pod’ and ‘Wildcard Slug”?

    If so, what values do you have set there?

    Thread Starter Chad Honea

    (@chad-honea)

    Thanks so much for the responses! Unfortunately…

    Permalinks update did nothing.

    Also, I should rephrase. I do have a page listing (of pods) and that is working fine. I’m using the Associated Pod set to my ‘locations’ pod and the Wildcard Slug is set to “{@url.2}”. No problems retrieving that list.

    I mean the pod itself, as select one of the pods types (say in this case, locations) go to view, and I get the 404. I can still edit it, the data is there, etc. It’s every pod on the site, which I’m using for locations, events, staff, media, and teams. Worked great before the update. Everything other than Pods is working fine on the site.

    I’m sure this is going to be something silly that I’m overlooking…

    Thread Starter Chad Honea

    (@chad-honea)

    Also forgot to mention that I’ve cleared cache with no result as well.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    What is the Pod Page URL for the ones you have set to {@url.2}?

    Thread Starter Chad Honea

    (@chad-honea)

    Pod list of locations
    /locations/
    Page at (test site)

    Location pod (@url.2)
    /locations/{location name}/ (test site)

    Other pods are similar:

    /teams/management/ (test site)

    /staff/{staff name} (test site)

    Thread Starter Chad Honea

    (@chad-honea)

    Ok, changing my permalinks to default shows the pods content. So…maybe my pods rewrites were reset with the update? It’s been a while since setting this up so I’m not remembering exactly how it was before. Playing with this now.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Your Wildcard Slug should be {@url.1} for the ones that live at /anything/{slug}/, {@url.2} would be /anything/another/{slug}/

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    When the wildcard slug is set, it will 404 the Pod Page if the item is not found from the slug.

    Thread Starter Chad Honea

    (@chad-honea)

    Wildcard slug…do you mean the Custom Rewrite Slug under Advanced Options for the Pod?

    The only place I see “Wildcard Slug” specifically mentioned is under a Pod page I have that lists my locations pods type. That page is really kind of irrelevant to the issue though as far as I can tell. All of the other Pods types that don’t have such pages that are affected in the same way.

    If you do mean the Custom Rewrite Slug, mine are all currently blank for each of my content types. Honestly I can’t remember if there was something there prior to the patch. I was thinking perhaps those slugs were wiped (I would think those should have been “locations”, “staff”, and “teams” in my case), but adding them back doesn’t seem to make a difference.

    Thread Starter Chad Honea

    (@chad-honea)

    So this appears to be an issue between WP permalinks and Pods. It worked flawlessly prior to my last update in which I updated to WP 3.7.1 and Pods 2.3.18. Site was current prior to the last update notice.

    Default permalinks show whatever pod I’m viewing (with the exception of some display issues). Unfortunately I need pretty permalinks.

    “Post name” (/%postname%/) permalinks give me a 404 for Pods. They are fine in any other page/post of the site, but no Pods content is accessible. I presume .htaccess is working fine since pretty permalinks are working elsewhere in the site.

    If I create a new pod of an existing Pods content type, viewing it shows a 404.

    If I create an entirely new Pod content type “test”, add a new “test pod” within “test”, then view (@ “/test/test-pod/”) I still get the 404. If I give that pod a custom slug of “custom-test” then go to “/custom-test/test-pod/”, I still see the 404.

    The quick fix of resaving permalinks doesn’t work.

    I’m definitely getting in a bind on this one with our client, and unfortunately I’m more of a Drupal dev. Following some other similar support threads without much luck. If anyone has any more insight I would appreciate it very much.

    Thread Starter Chad Honea

    (@chad-honea)

    Just switched themes from the premium them running on this site to the core 2013 theme. The pretty permalinks are working fine for Pods.

    So…this is some kind of issue with my theme, and not Pods?

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Did you try switching the wildcard slug to {@url.1}?

    Thread Starter Chad Honea

    (@chad-honea)

    Yes. No luck.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Looks like a tricky issue to track down, any chance you’d be interested in letting me have a go to help you out?

    You can securely submit temporary admin information here:

    https://pods.io/help/

Viewing 15 replies - 1 through 15 (of 24 total)
  • The topic ‘All pods pages are 404 after update’ is closed to new replies.