Oriana

Hi @mattmary

Apologies, I completely missed your messages until now.

Unfortunately I cannot provide the diagnostic report as I don’t have Matomo installed (I removed it back In November as soon as some code in the plugin was flagged as malicious).

As for your other question, my site is hosted with Sitegorund and they do indeed use NGINX Direct Delivery. Here is the description they provide:

“With NGINX Direct Delivery we will serve most of the static resources of your website (images, JS, CSS and others) directly through NGINX to achieve the fastest possible loading time. It works for all kind of applications without additional customisation.

For best results we highly recommend having NGINX Direct Delivery enabled at all times. However, if you need to use custom caching .htaccess rules for your static content you may need to switch it off.”

Hope this helps,
Oriana

Hi,

Just wanted to add that I had the same issue a week ago (3/11/22). After installing and activating the Matomo plugin (on a fully up-to-date WP website hosted on Siteground), I got an error page and immediately got a message from Siteground saying that they had detected malicious code in the recently uploaded files – specifically in: ../wp-content/plugins/matomo/app/vendor/matomo/device-detector-regexes/bots.yml.

The fatal error in WP mentioned this location: ../wp-content/plugins/matomo/app/vendor/matomo/device-detector/Parser/AbstractParser.php on line 300

It would be good if you guys could look into this, as at the moment it seems you cannot use the plugin if the site is hosted on Siteground.

Thanks,
Oriana

I’m closing this topic as I’ve now solved the issue.

It was indeed a problem related to my bootstrap version (the Yamm Nav Walker is made for Yamm 3 which is made for Bootstrap 3 or above). So I’ve updated my theme to the latest version of Bootstrap and the links in the responsive dropdown menu are now working correctly.

Hello… any takers?

I wonder if it’s related to my version of bootstrap (2.3.2 instead of 3), I’ll do some more troubleshooting…

Btw, it’s not iOS related as it’s happening on Android as well.

If anyone can shed some light and help me figure it out it’d be great! Ta!

Hi,

it seems that the team behind The Fox theme knew about this issue and included a fix in their latest theme’s update. Following their suggestion I’ve updated the theme to its latest version and that fixed the issue with the radio buttons, which are now selectable.

The only strange thing is that when I tested the form after the update, the form is working correctly on the live site (which is running contact form 7 v. 4.4.1), while the form stopped working on my local (MAMP) version (which is running contact form 7 v. 4.4.2)?. Basically on the local version of the site, now the radio buttons are selectable but I never receive the email with the message (although the form says that the message was successfully sent).

The only difference I can see between the 2 sites is the version of the Contact Form 7 plugin, so I thought I’d write it here for the plugin’s author information.

Best,
Oriana

No worries! ??

Have a look at this page, it may help you understand why yours aren’t showing:
https://contactform7.com/checkboxes-radio-buttons-and-menus/

Hi Debbie,

unfortunately the issue is still happening on my site (https://fluidads.com/contact/) as I haven’t changed anything – where/how exactly did you see it working?

I haven’t found a solution yet. I’ve opened a ticket with the theme’s support team as well, hopefully either them or somebody on this forum will be able to shed some light on the issue.

I’ll keep this thread updated if anything comes up.

Hi,

thanks for your reply.

I’ve already tested the same form on another WP site (with another theme) and there the radio buttons are working fine. My problem is that I need them to work with this particular theme.

Or did you mean switching to a default theme and then switching back to this one?

Ta,
Oriana

Never mind, I solved it! :))

FYI, the problem was that, within WPML string translation, strings were listed under 2 different contexts, one called “Cookie Notice” and one called “Plugin Cookie Notice”.
I was looking into the last one, which was showing strings from the php files of the plugin. When I looked into the first one, I found the actual string that controls the message of the configuration settings (the string name being “Message in the notice”) and adding the correct translations there did the trick. [big face palm]

Hope this can save some time to other people that may incur in the same oversight!

Oriana

Hi,

I’m having the exact same problem as SergioDev had (i.e. the string translations of the notice message are there but don’t work/show on the front-end) – did you find a solution in the end?

I’m working on a local WP site (via MAMP) that uses WPML (latest version). The site has 2 languages (Italian as default language and German), but the language for the strings is set to English, as suggested by WPML.

I followed the same steps as SergioDev:
1- installed and activated the plugin
2- Scanned the plugin for strings with WPML theme and plugins localization
3- checked via “see all the plugin’s texts” and found the english string for the notice message was already translated in both Italian and German (the string was marked as “translation completed”)
4-I re-saved both translations for good measure
5. I also set the administration language to English (but that made no difference)

Basically, although the english string is translated via WPML, the front-end of both sites shows the cookie notice message that you have in the Cookie Notice configuration settings (in my case the text in Italian).

Hope you can help!

Thanks,
Oriana

Ok, will try that, thanks!

Hi Richard,

first of all congratulations on your work with this plugin, I don’t know how you keep up with developing it and all the support questions! Good on ya! ??

I’ve just installed the latest version of your plugin (which includes the wpml.xml file) on a local WP site (via MAMP) that uses WPML. The site has 2 languages (Italian as default language and German), but the language for the strings is set to English, as suggested by WPML.

After installing and activating your plugin, the cookie notice works fine but appears in English on both sites (or in whatever language the message is written in the cookie law info settings). I tried to use WPML and scan your plugin for strings, hoping it would find the original English message and allow me to translate it into Italian and German, but the usual option “view the strings that need translation” doesn’t appear.

Besides, the scan shows that only 7 strings are found in your plugin and by creating a po. file I’ve seen that they’re not the ones that I need to translate:

msgid "Add New Cookie Type"
msgstr ""

msgid "Edit Cookie Type"
msgstr ""

msgid "New Cookie Type"
msgstr ""

msgid "View Cookie Type"
msgstr ""

msgid "Search Cookies"
msgstr ""

msgid "Nothing found"
msgstr ""

msgid "Nothing found in Trash"
msgstr ""

The plugin works fine with WPML when it comes to adding/translating the single cookies to show within the table on the privacy page table, but I have no idea how I can translate the the Cookie Notice itself and the text for the buttons on the settings page?

Thank you very much,
Oriana

Any takers??

Ok, it seems the culprit is the WPML plugin. When WPML is inactive the permalink works as it should – odd.

I’ll mark this as resolved as I’ll have to figure this out with the WPML folks…

Thank you so much Barry!! That was it! What a little number can do uh? I’m glad you kept digging until you found where the issue was, honestly I would have never thought of that!

Greetings from Italy!
Oriana