Dorian Cioban

Razumem.

Da li postoji neki na?in implementacije admin notice-a koji ?e javiti developerima da se plugin promenio i da je neophodan update/re-save/sync?

Problem je ?to padaju sajtovi dok su kupci aktivni i svuda se pale crvene lampice.

Ista pri?a. Sad ve? po tre?i put pucaju sajtovi u produkciji. Mora?u da na?em alternativu ovom dodatku.

PHP Fatal error: Uncaught TypeError: Illegal offset type in /home/xxx/public_html/wp-content/plugins/serbian-addons-for-woocommerce/lib/Checkout/Field_Customizer.php:160

PHP Warning: foreach() argument must be of type array|object, string given in /home/xxx/public_html/wp-content/plugins/serbian-addons-for-woocommerce/vendor/x-wp/helper-woocommerce/Traits/Settings_API_Methods.php on line 144

@natididi try ticking “Required” on the HTML field you have applied the conditional logic. It seems that a recent Elementor update broke this.

@milanbg probaj v3.5.10 sa GitHuba, to je meni re?ilo problem.

@dubravkica meni je verzija 3.5.10 sa GitHuba re?ila problem, odnosno sajt je proradio.

I can also confirm that by placing define( ‘WPCF7_VALIDATE_CONFIGURATION’, false ); in wp-config.php fixed the issue when using hCaptcha.

Hey AJ,

Thank you for your insanely long reply. ??

Unfortunately, due to time constraints we had to switch to Notibar which actually registers the inputs from Customizer in String Translation immediately.

To answer your questions: Yes, this is correct – the secondary language worked at first, but the primary didn’t. So, thinking it was a random bug, we replaced the primary language with secondary. This further broke the plugin and then we were stuck with the same buggy notices in both languages.

We are using a WPML lifetime license and are not locked out behind any features.

I’ve tried your code and it’s still bugged. If it matters, we are using Avada Theme (Child) + WPML. Both are at their latest versions as of today.

On a side note – why does the Notice bar activate immediately after being activated as a plugin? We used it on a live site, so imagine the panic when a placeholder that doesn’t do anything went live on a site with about 100+ realtime users…

Regards,
Dorian

Heads up – I tried the video tutorial and it completely breaks the plugin in the original language.

Message keeps returning:
[theme_mods_SDF-Child-Theme][easy_nb]message

Button keeps returning:
[theme_mods_SDF-Child-Theme][easy_nb]button_text

Button link keeps returning:
[theme_mods_SDF-Child-Theme][easy_nb]button_link

Reinstalling the plugin doesn’t help.

Out of curiosity, why didn’t you add a simple

<?php echo __( 'Your String', 'your-context'); ?>

for the message, text and button links and make the plugin instantly compatible with WPML?

Thanks Laszlo for the reply.

I will try both options you and Ramona have provided me with.

Hopefully Facebook video will be more flexibile in the future so we can easily add it as a regular slide.

Best,
Dorian

Wow, thanks for the quick reply.

So, the procedure was like this:

– We created a new slide
– In that slide we have added a simple text layer
– We copied the Facebook video link and generated a fully responsive code via iFramely
– We pasted that code in the text layer and it instantly loaded the video

The ideal situation for us would be if we could have a simple background image with a play button overlay. Once clicked (either background or the button), Facebook video embed loads (along with its code) and the user needs to click again on the Facebook video play button in order for the video to start. Is that currently possible in a non-code manner or even in the Pro version?

Thanks for the link, we will check it out.

A quick follow-up: the ignore option works perfectly. It would be nice to see a bulk select option and a larger listing of files that can be ignored in future updates.

Thanks,
Dorian

Great, thanks for quick reply!

Looking forward to it. ??

Same here. It just stopped working.

Here’s my error:

Count: 32
Last Error: 
2019-02-22 11:20:33: Google_IO_Exception: The stream IO handler requires the allow_url_fopen runtime configuration to be enabled in /home/onlytech/public_html/wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Deconf/IO/Stream.php:51
Stack trace:
#0 /home/onlytech/public_html/wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Deconf/Client.php(629): Google_IO_Stream->__construct(Object(Google_Client))
#1 /home/onlytech/public_html/wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Deconf/Auth/OAuth2.php(112): Google_Client->getIo()
#2 /home/onlytech/public_html/wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Deconf/Client.php(128): Google_Auth_OAuth2->authenticate('4/-QB0BNkOWlh9W...', false)
#3 /home/onlytech/public_html/wp-content/plugins/google-analytics-dashboard-for-wp/admin/settings.php(1254): Google_Client->authenticate('4/-QB0BNkOWlh9W...')
#4 /home/onlytech/public_html/wp-includes/class-wp-hook.php(286): GADWP_Settings::general_settings('')
#5 /home/onlytech/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array)
#6 /home/onlytech/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#7 /home/onlytech/public_html/wp-admin/admin.php(253): do_action('toplevel_page_g...')
#8 {main}
GAPI Error:

The functionality seems to be broken again, this is becoming a recurring joke.

I have no idea what Yoast team is doing, I’ll stop updating the plugin from now.

As soon as I disable Yoast everything works perfectly and og:images are visible.

They really need to stop messing around with crucial plugin functions.

Hey Arshid,

Yes, we had some older submissions with SUBJECT in them.

I will make sure to delete them since they are resolved anyways.

Thanks for the tip ??