Kunal

@atrais – I had disabled the Issues tab on the GitHub repo for some reason, my bad.

Logging is turned off by default. You’ll find the option to toggle it under the Settings.

Hi @atdugan

Thanks for using the plugin!

I believe the redirection URL depends on the Permalink settings you have enabled on your WordPress installation. From what I can understand, you have the default Permalink settings which is why you get redirected using page_id. If you change to post settings, you should get the page URL. Let me know if that helps.

@karhas I’ve released version 3.2.13, can you install that and see if it fixes the issue?

@jfejsa it’s working fine – the only logical explanation now is that there must be other plugins on your WP installation that might be conflicting with Custom 404 Pro. The only way to debug this is to disable the plugins one by one and see which one solves the issue.

If you’d like to see a demo of it working, check here: https://www.youtube.com/watch?v=5T5c8kB6B6c&feature=youtu.be

@jfejsa that’s fine, I’ll try to test on WP 4.9.6 + Divi 3.29.3 and see if I face any issues. Will keep you posted and thanks for the info!

@koolheric thanks for using the plugin! Could you try removing the plugin and installing it again from scratch? If that still doesn’t work, could you tell me the WordPress and plugin version you’re using?

@karhas thanks for using the plugin! I’m assuming you’re upgrading from a previous version. Could you remove the plugin altogether and install a fresh version? Remember to remove it from the Plugins menu as that will also cleanup any database tables. Let me know if that works!

@jfejsa thanks for using the plugin. Can you try disabling the Divi theme and see if the plugin saves the preferences? If not, could you try removing the plugin and installing it again? It’s possible that there might be other themes/plugins that interfere with the workings of this plugin and I just want to make sure of that.

Lastly, what WordPress and plugin version are you using?

@ericsharp79 can you please update to the latest version of the plugin and check if you’re still facing this issue?

Apologies for the delayed response — as mentioned in the plugin description, I rarely check the WordPress Support section.

Thanks for using the plugin!

@dlwnz I see. Thanks for the bug report, I’ll take a look and release a fix ??

@elegance46 not a problem, just want to check one more thing – is your PHP version less than 5.5? If yes, then this error will occur because of the way the code is written.

I’ll try to make a fix for this in the next release. Meanwhile, if it’s possible for you, you can try a higher PHP version on a sandbox and see if the plugin works for you. Thanks for the bug report though! ??

@elegance46 okay I’ll look into it, have you tried re-installing the plugin?

@elegance46 you need to deactivate the latest version (after upgrading) of the plugin and then activate it.

@filout re-installing the plugin gets you to a fresh start and re-initializes all the tables. This error has been fixed in 3.0.5 so going forward (in future updates) you’ll not see it – that’s just how the WordPress Upgrader method works unfortunately.

Technically speaking, you should not see this error when doing a fresh install. Let me know if you do.

@dlwnz great, thanks! ??