• Resolved maximilianknap

    (@maximilianknap)


    Maybe this is something that can be fixed easily, but I write this also as a warning to everyone using Popup Maker AND WPML together.

    When activating the plugin I realized that all posts and pages lead to a 404 error page (not found). I am using a custom permalink structure like http://mysite/%postname%/ as the post url.

    Short: I had to deactivate and immediately reactivate all WPML plugins, I am using:
    – WPML Multilingual CMS (main plugin)
    – String translation
    – WPML Media

    After that everything worked as before.

    Longer: Switching to the default permalink structure also temporarily solves the issue. My first guess was a .htaccess issue, but it was untouched. Typically (google says) this kind of issue is a result of bad or missing .htaccess file, but not in this case.

    Somehow This plugin interfers with string translation, I guess. We are using translations for permalinks, too, maybe this is some piece of information that could help reproduce the issue.

    Cheers
    Maximilian

    https://wordpress.org/plugins/popup-maker/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Daniel Iser

    (@danieliser)

    @maximilianknap – Sounds more like a glitch in your specific system / setup. We have plenty of users that use WPML with Popup Maker and no reports like this.

    Also nothing you pointed to (to me) so far indicates anything was actually caused by PM. IE all of your solutions involved other plugins & core settings.

    That said I just fired up a test install and activated WPML with a few translated pages etc, then added PM and saw no issues.

    Sounds like something triggered your permalinks to need to be flushed (something we don’t do because we don’t have public urls in this plugin at all).

    To clarify we have 0 functionality that could affect permalinks, rewrite rules etc. All of our post types are registered just like any other, marked private (no urls/permalinks) etc. We also do things by the book in terms of translating strings as well so not sure I can see an issue resulting from that either.

    For the most part there are 0 hacks or hacky types of code used for this plugin. We do things as closely to the WordPress codex ways as possible to limit issues like this from ever occurring.

    Best guess your permalinks were corrupted and simply needed to be flushed (go to Settings -> Permalinks and simply click update).

    If you can track down a specific issue then I would be happy to help, but based on what you have listed here I see no issues with PM that we can help with.

    Thread Starter maximilianknap

    (@maximilianknap)

    Thanks for your quick reply! You are right, that type of issue could be caused by other plugins too.

    Unfortunately “flushing” the permalinks (by clicking update) did not solve the problem. I tried this first because it is the most popular solution for that type of error according to google.

    Did you set up slug translation in your test scenario? That might be a rather rare combination among WPML users but I’m not sure about that. Could also be a WPML issue. At least it’s reproducable. If there is any kind of debug info I could provide or a way to digg deeper, please let me know.

    I’m just glad I found a workaround – disable WPML, re-enable WPML and everything works fine again.

    Maximilian

    Plugin Author Daniel Iser

    (@danieliser)

    @maximilianknap – Hmm, could you export your site in a way that I could load it on a test / local server and try to duplicate?

    Also have you submitted a ticket with WPML yet? They may have better answers.

    The only possible issue (and this would still be on WPML not PM) is that we add additional post types, which if im not mistaken triggers a rewrite rule update. If WPML is filtering that somehow they may not be doing it in a way that it catches new post types. IE they may only do it upon activation of their plugin. Which would mean any plugin that added new post types afterwards (with the slug translation on) could trigger this.

    Hope that helps.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Activating plugin results in 404 error for all posts and pages’ is closed to new replies.