Gergely Imreh

I’ve sent the author a patch to update the plugin, and by that time he had some changes added already. Have you updated to the latest plugin version, and see if this still happens? I’m using version 2.4.4.

I use Polylang for multilingual support, and still have this issue. Had to disable monitoring changes to blogposts, otherwise every newly published post creates a redirect from the frontpage… Only started in the last couple of weeks, I think.

Are you using Polylang for multilingual support?

I have this, on every new post, Redirection adds a redirect from frontpage to the latest post for the specific language, if I have Monitoring enabled for Modified posts. It started relatively recently (last few weeks).

That’s too bad, because automatically monitoring moved posts is a good feature, and it was working before (at least I think:)

I think I have the same thing as well, using Redirection and Polylang for multilingual. Whenever a new post is published, a redirection seems to be created to send the frontpage traffic to the post.

Would very much like this not to happen (it started just recently, I think). Any info what might be happening?

Hi, the latest version seem to have resolved the issue, thanks! ??

I think 1.6.5 worked fine, no such problem.

To try the development version from upload, I think I’d have to uninstall/reinstall the plugin, and can’t really do that with our live site, so will wait for the released update, thanks anyways!

Hi,

Sorry, it’s in the admin interface. Here are some screenshots, first with no cache or cache cleared, normal behavior. Then with caching only shows one language’s categories.

polylang categories issue

The post editor in the admin is is also affected (posts also don’t show the their own language’s categories, always just one particular language’s).

Let me know if there’s anything else I need to clarify! ??

Thanks for checking it out. I’m not considering moving to a new domain mapper plugin yet, as the NG by itself (all other plugins disabled) does already have this behaviour, and if another plugin corrects it, that’s more likely two broken things accidentally cancelling out.

I’ll wait for the new version of the NG at this time.

Let me know if I can be any more help with this issue, and thanks a lot!

No, the issue is just with pages. Posts work fine.

Examples from the live site:

1) Page (wrong)

The page https://apc.io/products/ works with stub, and using curl -I https://apc.io/products/ to see the header it reports Link: <https://apc.io/?p=976>; rel=shortlink.

Then using the shortlink https://apc.io/?p=976 from the header, I get 404 when NG is enabled (like right now).

2) Post (correct)

The post https://apc.io/blog/2014/02/27/apc-in-the-fox-den-mwc-2014/ works with stub, and using curl -I https://apc.io/blog/2014/02/27/apc-in-the-fox-den-mwc-2014/ to see the header it reports Link: <https://apc.io/?p=1208>; rel=shortlink.

Then using the shortlink https://apc.io/?p=1208 from the header it loads correctly (200).

I’m sorry, it is a corporate site, and I don’t think giving the credentials for the live site is appropriate.

I think everything you are asking was in my previous answer already, but I try it again.

When the mapping plugin is enabled, https://mapped-domain.hosting-domain.tld/ just redirects to https://mapped-domain.tld/ all the time. When the mapping plugin is disabled, https://mapped-domain.tld/ redirects to https://mapped-domain.hosting-domain.tld/ all the time

Not a single time does a ?p=123 link work when it is a page type. When it’s a blogpost type it does work correctly either with name or with ?p=123 form, whether or not the domain mapping plugin is on. Thus I do not think it’s the domain mapping issue.

The “default” permalink structure that you say should resolve, does not in fact resolve, when NG is enabled, but only for the “page” type.

Hi, yes, I’ve deactivated the Domain Mapping one as well. I re-checked it right now.

NG on, then when mapping plugin on:

* unmapped/pagename -> 301 moved permanently to mapped/pagename
* mapped/pagename -> 200 and header includes mapped/shortlink
* mapped/shortlink -> 404 (the reason for the bugreport)

When mapping plugin off

* unmapped/pagename -> 200 and header includes unmapped/shortlink
* unmapped/shortlink -> 404

To me it looks like it’s not the mapping plugin….

The shortlink I refer to is the domainname/?p=postnumber format (that’s reported in the header of http requests, and when using NG it does not resolve for pages but 404 out (that’s the bugreport). Does this answer your second question? I’m not totally sure I understand it correctly.

With NG 2.0.66.27 and WP 4.0 the short codes stopped working for me too, though only for pages. Blogposts shortlink keeps working, but every page shortcode results in 404.

Using version 12.02.08, manual backup runs fine, background (and scheduled) backup never finishes.