mines.io

Whenever there is a 404 problem with a URL in WordPress, regenerating the permalinks may solve the issue.

Doing so, it doesn’t usually change the .htaccess file, but it rebuilds the URL routing structure, which is stored internally on the DB.

I think it would be nice to trigger a permalink rewrite action on plugin deactivation.

Thanks for your feedback.

Ok Carlos, I get it now. Please let me think about it.

Can you confirm me what are the values of “WordPress Address (URL)” and “Site Address (URL)” on your WP setup, under Settings > General?

Thanks,
Mines.

Ok,

I am looking into this now. Please let me investigate.

Thanks,
Mines.

Hi Fred,

Please do the following after the plugin is deactivated and let me know if the problem persists:

Go to Settings > Permalinks and click “Save Changes”

So If I understand correctly, you currently have:

https://yoursite.com/blog/category/post-name

And want to have:

https://yoursite.com/blog/post-name

Is that correct?

Do you have WordPress installed on a folder or is it on the root public website folder?

Regards.

Hello,

I don’t clearly understand what you did when moving “/blog” to root. Could you please explain it further?

Thanks,
Mines.

Hello all,

I’ve added support for custom pagination_base on the development version of the plugin, which is available at:

https://downloads.www.ads-software.com/plugin/no-category-base-wpml.zip

If there are no issues with it, I will soon update the stable version to merge this fix.

Thanks.

Thanks for the heads up Sergey. Did that!

Thanks anyway for the feedback, Dan.

Thanks for the feedback

I don’t know why this topic was marked as resolved without being so.

I’ve added the code to fix the issue for WordPress 3.4. Many thanks for your feedback.

Please let me know if there are any more issues.

Thank you for the attached code. A new version of the plugin has been released which should fix the issue.

Thanks for sharing newbieee. I will take a look at it and change the plugin if it doesn’t break other setups.

Hi Dan,

Could you please share some info about the unpatched XSS vulnerability so I can take a look at it?

Thanks