[Plugin: 404 Redirected] 1.3.1 Loops endless – not usable

I can’t seem to duplicate this bug. I just tried it on my personal site and the pagination seemed to work fine.

I tried paginating the category, which worked.
I paginated the sub category browsing – worked.
I paginated a post that was assigned to the sub category. Also worked.

Is there anything else that might point me to the correct direction?

1.3.2 is out.

you checked cat/sub_cat/page/ ? cat/page or /page works. maybe a changed permalink thing?
1.3.2 still produces the loop :/

Yeah I checked…

/blog/cat/2
/blog/cat/post/2
/blog/cat/subcat/2
/blog/cat/subcat/post/2

All worked.

Do you happen to have a automatic redirect in the system already for those particular URL? If the redirect is already in the system it *might* be causing a problem. If you deleted it I wonder if it would come back.

i have from a seo a second 404 monitor (no redirect) – just moved my page from joomla to wordpress – so a lot redirects are needed ?? i can’t trigger all with .htaccess

blog is an article – what works. i got the error with pages. with version 1.2 all works fine.

hmmm – any other hint?

I am still confused. Lets try this…

You’re have a problem with Posts or Pages?
What is your Permalink setting set to?
Can you send me a actual copy of the log file from the server? Such as the IIS or Apache log? A snippet of the problem will do.. email it to [email protected]

if you could email me database dumps of wp_wbz404_redirects and wp_wbz404_logs tables too that would be really great.

the problem comes with pages. /%pagename%/ is set in permalinks BUT i use Permalink Editor where i can set cat/subcat/PAGENAME when editing a page (haven’t found a better way to setup this structure because i need some pages just plain e.g. /legal some like /products/fruits/banana).

ok, fixed it. in 1.2 i defined global $permawasdone; $permawasdone = 1; in permalink-editor and function wbz404_process404() { global $permawasdone; if ( $permawasdone ) { return; } in frontend.php (404).
second `add_action(‘template_redirect’, ‘wbz404_process404’,99999);
add_filter(‘redirect_canonical’, ‘wbz404_redirectCanonical’, 99999, 2);
`

seems to works now ?? sorry^^

Wouldn’t you set that up simply using the parent page feature…

/products – page
/fruits – page – Parent Products
/banana – page – Parent Fruits

That would give you a permalink of /products/fruits/banana

Very similar to the Weberz page of Dedicated Servers where we have:

/services as a page and /services/dedicated-server-hosting as a sub-page of services.

What you have done with your fix is completely bypass the 404 processing for any page that you have a custom permalink for using the other plugin.

I would be interested in knowing how the other plugin is setting the permalink for the page as they aren’t changing the official permalink for the page in the WP DB. My guess is that they setup a template_redirect function that finds the permalink typed in and they keep a DB table that matches permalinks to page id’s. Then they load the appropriate page id based on the custom permalink. This would work fine unless someone was checking the 404 status of the page like we are.

If the above is true.. they should modify their plugin to report the custom permalink page as not being a 404 much like Yoast does with his sitemap_index.xml URL in the WordPress SEO plugin.