Limited Support
Our team is currently on holiday, so support will be limited during this period. Response times may be slower than usual, and some inquiries may be delayed. We appreciate your patience and understanding, and we’ll resume our usual support by the end of August.
I'll use my dev site URLs in this description, but I've confirmed that the problem occurs on a site with a "real" TLD. This project uses Bedrock, which modifies the WP folder structure. As a result, the "WordPress Address" and "Site Address" WP settings are different from a vanilla WP install:
WordPress Address: https://geoex.test/wp
Site Address: https://geoex.test
The site's blog is at https://geoex.test/blog, so there is a Custom Structure in Permalinks settings: /blog/%postname%/
The wpDiscuz subscription form submits and calls the addSubscription() method in WpdiscuzHelperEmail. At line 62, this redirect takes place:
wp_redirect(get_bloginfo('wpurl') . '/' . $httpReferer)
The problem is that the resulting URL for the redirect starts with:
instead of:
This, of course, results in a 404 error.
the issue doesn't have any relation to the wpDiscuz plugin. This may come from your website configuration. If you send the admin login details to info[at]gvectors.com email address, the developers will check the issue.
@astghik, I have sent you credentials for the project's staging site. I have a redirect in place as a workaround: wp/blog/(.+) to blog/$1
The developers can't check the website by accesses you've sent, because of the plugin editing is disabled.
Posted by: @jeffrey-zienowicz
I have a redirect in place as a workaround: wp/blog/(.+) to blog/$1
You can continue to use this way, till we will update the version. In the new version, this issue is already fixed.
@elvina, Ah, right: DISALLOW_FILE_MODS is set to "true." I could change that for you, but it sounds like you've identified and fixed the issue for the next release, so I take it you don't actually need to do any analysis of my site?
I could change that for you, but it sounds like you've identified and fixed the issue for the next release
ok, please wait for an update.