-
Posts
-
Hi,
I wanted to have the standard 2017 demo somewhere in order to easily check all possible Enfold elements.
I did a clean WP installation, 2017 demo import.Submenu Portfolio Overview Pages works fine when permalinks set to plain. As soon as permalinks are set to “Post name” the links in that submenu give 404. This happens ONLY on that submenu, everything else continues to work just fine with “post name” permalinks, even the main Portfolio menu entry continues to work just fine.
Switch back to plain permalinks, all works again…All plugins disabled same result, compression in Enfold disabled same result. Re-imported demo, same result.
It has definitely nothing to do with any plugin or setting, because the same happens on a clean WP install with only Enfold + child theme + 2017 demo import. You can check that yourself.
This behaviour is a complete mystery to me. I don’t know where to look anymore. Can you help?
Rob
Token in private box
Forgot to mention (added later):
On a clean WP installation with Enfold + Enfold child + 2017 demo imported, then the issue starts to happen when you add anything to either the main menu or the footer menu. Even when you remove the new menu entries later the issue is persistent: 404 on all submenu link below PortfolioHey Rob,
Thank you for the login, I deactivated all of your plugins and changed your permalinks to “Post name” and the sub-menu portfolio items are working correctly, please clear your browser cache and check.
I’m not sure what was causing the 404’s so try enabling your plugins one at a time and re-check your portfolio sub-menu for the error again, if you find the error again try re-saving the permalink structure again and if this doesn’t solve then note the plugin as it could be the conflict.Best regards,
MikeHi Mike,
Thanks for taking a look at this. I will do as you suggested, even though I did it a few times before :-)
I’m still stumped as to why this happens, I tested 3 more times on local installations, following the same procedure every time, and sometimes the issue happens and sometimes it doesn’t…even on a clean install without plugins.Switching between permalink structures sometimes seemed to trigger it, sometimes it was adding something to the menu. Other times doing the same things everything continued to work. Like I said: I’m stumped.
Of course I always cleared the cache, had Enfold compression disabled, opened in a private window etc.I will test some more, and come back here if I find something relevant to mention.
Thanks for the help so far!
RobHi,
Very good, we will leave this open to hear back from you.
Please note that when switching between permalink structures WordPress writes to the .htaccess file on your server to assign this change, if the write doesn’t take place correctly the first time saving again often corrects. There are many server issues that could cause the “hiccup” but it’s usually not a big deal because normally the change is only made once.Best regards,
MikeHi,
I think I found the reason for the strange behaviour with the submenu links: they start to happen when I add the Falang language switcher to the main menu — and while active the permalink-set-to-postname issue cannot be resolved, no matter how many times you save the permalink settings. Yet with permalinks set to plain everything works fine with the language switcher in place. I will take that up with the developer to see what the reason might be for that.
But it is still strange that it would only affect the Portfolio submenu items, while all the rest (all other submenus included) continue to work as advertised :-) Anyone have a good explanation for that so I can add that in my mail to the plugin developer?
If you could keep this open for now, I will report here when the issue has been solved. Thanks again,
Rob
Hi,
Glad to hear that you found the conflict, I’m not sure why this would only affect the portfolio sub-menu items, perhaps the plugin author will know, I see that he has released different versions of the plugin for different themes, perhaps this is why?
We will leave this open to hear back from you.Best regards,
MikeHi,
In the meantime we found out why this happened: when the Portfolio Items and the Portfolio Categories are checked in the Translate Options of the Falang plugin (marking them as translateable items). then the issue described above happens. When they go unchecked in the plugin, everything works as it should also with the postname permalinks. Which is why I sometimes had the issue and sometimes not (depending on checkmarks set within the plugin config).
Faboba (the developer) is already working on a fix to solve this. Once done and checked I will report the results here.
Thanks for your time and help and for pointing me in the right direction!
Rob
Added remark:
The extensions which were released for Falang are not different versions, they are just enhancements for various theme platforms, to make the translations from within each theme platform’s interface. They are enhancements, not different versions of the main plugin.Just to clarify.
- You must be logged in to reply to this topic.