LeonN1960

Hi Elena,

I tried at first to only change the absolute path to only the relative path, but that was not enough (same error 403). But when I added the code to the .htaccess file in the wp-content folder it worked fine.
First try when I added this additional code at the beginning of the .htaccess it still gave the error, but when I shifted the code to the end of the file it was perfect.

Assumably this will be a feature in the plugin on short notice?

Thanks for support!

I prepared a copy on another website, which gives the same result.
https://www.sportscarsofengland.nl/en/widget-search-hippevegetarier/
Currently system file protection is switched off on this website.

So please, could someone give more clearity on this subject.

I configured SiteKitGoogle also for the Google Analytics universal version and also extended with Google Tag Manager. No problem on this website as I see now. So it is weird where this comes from…

James,
Please find the requested details here… https://imgur.com/a/7myhThL

I prepared two pie charts next to each other, with manual data. So not to complex.
Next to this I created a similar solution on another website (https://famnabuurs.nl/charts) and there it works fine, nothing wrong there. But could be since I did not connect GA in my Site Kit in this website

Additional input:
When I display the page via the WordPress dashboard it all looks fine, also in Chrome. But, when I log out from the dashboard and I refresh the page it does not show up again.

Please, some can help me solving this issue?

It looks like a version conflict ….
The plugin visualiser has a js module called render-google.js. In line 454 it tries to load a google object and this is the response:’google is not defined’.

Therefor I assume it is a conflict with the Site Kit Plugin since that is the only plugin referencing Google items ….

Hi,
I tried with the additional plugin, but I saw no difference.
Currently I have the SiteKit plugin active, and then Chrome does not show my charts; Firefox sometimes does.

Hi Riddhi,

I dropped the translated files (.po and .mo) in this folder: \wp-content\languages\plugins\sp-news-and-widget
And all translations work fine except for these four …

And when I change the code it also works fine, but thats not the way to solve it.

Any idea’s left?

Hi

That’s a bit weird. In the plugin-version I use (4.3) line 13 contains this statement:
‘name’ => _X(‘News’, ‘sp-news-and-widget’),

But when I refer to the wordpress code reference it requires this:
_x( string $text, string $context, string $domain = ‘default’ )

So, using the _X this way it says the context is ‘sp-news-and-widget’ and that corresponds with the presentation in POedit. POedit indicates that the context is ‘sp-news-and-widget’. But the live plugin does not translate it to my language string.
I created this language string file from the online translation strings…
Could you please test it with the Dutch translation set?

School data is mainly for publishing on the map.
Yes, I am comfortable with coding PHP, html and CSS. So if you could point me to some additional support information that would be great.
Translation is not a problem; I will take the dutch language as the starting point and adjust the terms I want to use.
Would be great!

Hi,

I am not able to login via envato, I lost my credentials and the base mailadres I used there does not exist anymore. Is there another solution to be helpful?

Best regards,
Leon

Hi RealMAg777,

Thanks for approving my request. I hopefully can help with further improvements.

In the current development base I translated all literals, but still quite a lot of text is untranslatable. Could you please check and extend the list of translatable items?

Best regards,
Leon

@larryz: No, I made a plugin myself for other purposes. That plugin used to make a connection with google calendar but that did not function anymore. But in the php_error.log I saw quit a bit of fatal errors of Caldera, like the ones mentioned above. When I deactivated the Caldera plugin, my problem was solved, also when I restored previous version and activated this

Same issue here. Re-installed the previous version and problem was solved