Ok, found out that generated url didn’t included “/sites/8/” which is for my sub site. As a reminder I installed plugin on a multisite and as I asked before you said is compatible but not make it network activate which I did.
Is there anyway that I can get correct generated url for a sub site?
Last and an important thing that I believe this happened in your recent update since I was able to create a correct xml url on previous version but not with new version. Can you please check?
Thanks
-
This reply was modified 4 years, 1 month ago by
smithjhsn.
Hi @smithjhsn,
Sorry to hear you’re having issues with the plugin.
For a multi site it is important to install the plugin in the network admin (so not the specific web site) but to activate it on the specific web site.
If you did that it should work correctly.
You mentioned that it worked correctly on an older version. Do you know what version that was?
yes, I did what you mentioned and yes previous version worked as expected(generated correct url for subsite) but not in recent update.
-
This reply was modified 4 years, 1 month ago by smithjhsn.
OK, I will have to investigate the issue.
You should still be able to manually send the correct feed url to Google right?
Are you familiar with working with WordPress filters? If so, you could use the ‘wppfm_upload_dir’ filter to get the correct url to the feed in the feed list. You could use something like:
function corrected_feed_url( $url ) {
return 'put the correct url to the uploads folder here without end slash';
}
add_filter( 'wppfm_upload_dir', 'corrected_feed_url );
After implementing this filter you’ll have to regenerate the feed and than it should have the correct url.
To confirm just downloaded 1.19.1 and as I said worked as expected but not 1.20! When is your next update that can patch this bug?
I prefer to use previous version till new update if it will be sometime soon.
Thanks
-
This reply was modified 4 years, 1 month ago by smithjhsn.
-
This reply was modified 4 years, 1 month ago by smithjhsn.
Yes, I will work on it tomorrow and I’m pretty sure I will have it solved before release of the next update which is expected to be released next week.
I’ll keep you informed.
Appreciate. This plugin and your support is awesome 🙂
Hi @smithjhsn,
I was able to recreate the issue. Fixed it and it will be incorporated in the 1.21.0 version I expect to be released next week.
Hi @smithjhsn,
You now can update our plugin to the latest version and that will solve the issue you reported. Thanks for reporting it.
I will close your topic, should you still have a question about it don’t hesitate to reopen it again.
Stay safe and healthy.
