Frank

Great – many thanks! Already updated the plugin and the domain is correct now, without the folder.

When using double opt-in you could take advantage of the confirmation page to setup a destination page goal in GA with a regex match.

The link format of the confirmation page is (in my case):
https://mydomain.com/?wysija-page=1&controller=confirm&wysija-key=xxxxxxxxxx&action=subscribe&wysijap=subscriptions&wysiconf=xxxxxxxxxxx

So the regex to match this page could be something like:
/?wysija-page=1&controller=confirm&wysija-key=.*&action=subscribe&wysijap=subscriptions

Hi Richard – that’s exactly what I did: disable all plugins and enable them one by one to check if the behavior of media uploads changes.

In fact, that’s how I found that Cookie Law Info seemed to be causing the problem. And on my site I can reproduce the issue every time I upload something. Even with all other plugins disabled, and only Cookie Law Info enabled, the media uploads go to /uploads/2013/10/.

For the records: I also tried reinstalling Cookie Law Info as well as deleting all settings and reset – but no luck. WordPress is at 3.8 now, but same problem ??

Anyways… if I find a solution, related or not to Cookie Law Info, I will post it here.

Regards,
Frank

I checked with a default theme (Twenty Thirteen) and the result is the same: uploads go into /uploads/2013/10/ with Cookie Law Info enabled and into /uploads/2013/12/ with Cookie Law Info disabled.

However, I also checked on a different website and there it’s working fine, no matter if Cookie Law Info is enabled or disabled.

So as you say, it’s probably not Cookie Law Info causing the problem.

I rolled back to the old version of the Pytheas theme which seemed to work better with Polylang. As to the new theme, I did not try to add the language switcher to the menu… Sorry for not being more helpful & good luck!

ok – the error messages are gone in the development version.

However, back to the initial problem: the fact that I got error messages means that polylang can read the wpml-config.xml, so it’s in the correct folder. Removing the lines about taxonomies also removes the error messages and the wpml-config.xml works with the old version of the Pytheas theme. So I believe the problem with the strings not showing up in the string translation table must be linked to the new Pytheas theme…

These are the error messages I received in languages -> settings:

Warning: array_diff() [function.array-diff]: Argument #1 is not an array in /users/myuser/www/wpfolder/wp-content/plugins/polylang/include/admin.php on line 420

Warning: array_unique() expects parameter 1 to be array, null given in /users/myuser/www/wpfolder/wp-content/plugins/polylang/include/admin.php on line 420

With wpml-config.xml:

<wpml-config>
    <taxonomies>
        <taxonomy translate="1">services</taxonomy>
        <taxonomy translate="1">portfolio</taxonomy>
    </taxonomies>
    <admin-texts>
        <key name='options_wpex_themes'>
            <key name='home_tagline' />
            <key name='home_highlights_title' />
            <key name='home_portfolio_title' />
            <key name='home_blog_title' />
        </key>
    </admin-texts>
</wpml-config>

I assume it’s because I added taxonomies in wpml-config.xml that are already taken care of in the settings “customized taxonomies”.

The file name is correctly spelled, no upper case letters. I also tried putting the file in different subdirectories, including the one of the theme but it didn’t change anything.

I’m quite sure that polylang reads the file because at one point it gave me an error message in the settings page (when I added some taxonomy strings for translation that were already covered in the settings).

Anyways, I think it has something to do with the new Pytheas code and maybe with the fact that the options framework is now integrated in the theme (no need to install the plugin). For now I rolled back to the old version of the theme and the wpml-config works without problems.

That’s really strange… I tried again, changed options, saved, deactivated all other plugins, but still no luck. Also tried “reset to default” in the theme options, saved, changed one option, saved again – but no change: the strings don’t show in Settings -> Languages -> String Translation. ANSI/ UTF-8 encoding for wpml-config.xml make no difference neither… Any idea what else I could try?

Hi Chouby – thanks for your quick response.

All values in the admin theme options are filled (some with the default and some customized). File permission for wpml-config.xml is 0644 and the polylang folder 0755.

I also found the information in options.php and took it from there. The part you quoted is identical in the new version:

function optionsframework_option_name() {
    $optionsframework_settings = get_option('optionsframework');
    $optionsframework_settings['id'] = 'options_wpex_themes';
    update_option('optionsframework', $optionsframework_settings);
}

You can check pastebin for the full options.php.