Plugin Author
Chouby
(@chouby)
I really don’t see how WP 3.6 update would be responsible of that.
I realise this may have to do with the theme
Do you mean you made a test with a default theme and everything is working making you think that this could be a conflict between Polylang and your theme? Is your theme freely downloadable?
We are updating a site that looks like it has been through several rounds of development. It is rather messy.
The theme is this one:
http://www.gallyapp.com/tf_themes/?theme=Gaia
But an older? version.
We had the site almost ready to launch, using Polylang and
all of the current settings. It was running fine.
Then our host automatically upgraded us to WordPress 3.6, and suddenly we are having issues. The issues seem to revolve around url modification in action hooks?
I have installed a fresh WP 3.6, and imported all of the data, without all of the settings, and that changed some of the output.
Because Polylang is tied into many modifications in the theme (not that we changed any actions or filters, just modified presentation code), it is a lot of work to test in one of the default themes. But, I switched to different default themes, and I can see some things to work on.
But we are still having this problem:
/en/wp-content/themes/Gaia-tf2/images/search_button.png
See the ‘en’ ?
That is causing some of our files to fail to load.
Do you have any suggestions on what to look for as I go through the code?
Thanks very much for your support.
And Polylang really is a nice plugin.
Plugin Author
Chouby
(@chouby)
/en/wp-content/themes/Gaia-tf2/images/search_button.png
Are you able to identify the line of code in your theme which is generating this wrong url and report it here?
Hi Chouby,
Still working on this.
After switching out themes and some other activity, we are seeing improvement.
But Polylang is still doing url rewriting on image paths in our searchform.php.
Plugin Author
Chouby
(@chouby)
Are you using the latest version of Polylang? The url rewrite in search forms should have been solved in v1.1.5 (and if I remember well, this bug appeared with WP 3.6).
Ahhhh ….
We had been holding off updating the plugin.
Just did so, and that fixed the image issue.
Thanks very much!