draganmilanovic

hi there

i have disabled transliteraion plugin but same issues are present.

`t.every is not a function. (In ‘t.every(r.isEmpty)’, ‘t.every’ is undefined)</p> <pre class=”wp-block-code”><code>in WidgetNull in WithWidgetSlug(WidgetNull) in ConsentModeSetupCTAWidget in WithWidgetComponentProps(ConsentModeSetupCTAWidget) in DashboardMainApp in DashboardEntryPoint in RestoreSnapshots in ErrorHandler in ThemeProvider in StrictMode in Root`

• This reply was modified 8 months, 1 week ago by draganmilanovic.

hi there,

yes i submitted all via the form a few moments ago. the same problem is in icognito mode, different browsers etc. Enabled and disabled various plugins but seems to be crashing for a unknown reason. We tried to trouble shoot by ourselves but unsuccessful even did a deinstall and reinstall of the site kit.

we have some small leprecons running around on the site make a bit of a mess it seems … ??

Hi There, the issue is still present. Any other fix maybe available

Regards

Dragan

Cao Ivane,

uradjen je updejt i aktiviran je bio plugin ali nije resio problem, i dalje isto problem. posle updejt je cache ocisten i sve ostale radnje. Ako zelis daj mi vas mail pa cu poslati pristup za stagin sajt pa da mozete direktno da vidite gde i sta.

Pozdrav,
Dragan

slican problem sam imao pa smo resili kroz sledece:

/**
 * Custom currency and currency symbol
 */
add_filter( 'woocommerce_currencies', 'add_my_currency' );

function add_my_currency( $currencies ) {
     $currencies['RSD'] = __( 'Currency name', 'woocommerce' );
     return $currencies;
}

add_filter('woocommerce_currency_symbol', 'add_my_currency_symbol', 10, 2);

function add_my_currency_symbol( $currency_symbol, $currency ) {
     switch( $currency ) {
          case 'RSD': $currency_symbol = 'RSD'; break;
     }
     return $currency_symbol;
}

mozda vama to pomogne isto.

We did some testing with all other plugins disabled them and 1 by one enabled, also the theme designers checked it out. This happened after the recent update when you implemented the fix for a specific theme.

https://ibb.co/DRZr8DF

https://ibb.co/7YwQWVC

https://ibb.co/WBdHjz3

Hi There,

yes, i understood this part already the first time and understand why this can happen, i am not blaming anybody here as i know what a small error/typo can mean. However, what i did when we figured it out, we reinstalled LOCO, did a copy from custom format to “original language” format and we did not have the issue. (and deleted the old)

Yes, probably something we did wrong in the translation however when we made a copy from the identical file it simply worked…

Thats the part which we did not understand in our case…

BTW thanks and keep up the good work and support this means a lot for our builds.

cheers

Dragan

Hi Tim,

in principle i would agree with you. But what happened is we got this error:

PHP Fatal error: Uncaught ValueError: Unknown format specifier

Now we have a full errorlog and syslog for your available if you want to have a look at it.

[17-Mar-2023 13:16:54 UTC] PHP Fatal error:  Uncaught ValueError: Unknown format specifier " " in /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/Purchase.php:130

Stack trace:

#0 /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/Purchase.php(130): sprintf()

#1 /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Task.php(490): Automattic\WooCommerce\Admin\Features\OnboardingTasks\Tasks\Purchase->get_content()

#2 /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php(406): Automattic\WooCommerce\Admin\Features\OnboardingTasks\Task->get_json()

#3 /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/API/OnboardingTasks.php(741): Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskList->get_json()

#4 [internal function]: Automattic\WooCommerce\Admin\API\OnboardingTasks->Automattic\WooCommerce\Admin\API\{closure}()

#5 /home/ssidoors/prodato.rs/wp-content/plugins/woocommerce/src/Admin/API/OnboardingTasks.php(740): array_map()

#6 /home/ssidoors/prodato.rs/wp-includes/rest-api/class-wp-rest-server.php(1171): Automattic\WooCommerce\Admin\API\OnboardingTasks->get_tasks()

#7 /home/ssidoors/prodato.rs/wp-includes/rest-api/class-wp-rest-server.php(1018): WP_REST_Server->respond_to_request()

#8 /home/ssidoors/prodato.rs/wp-includes/rest-api/class-wp-rest-server.php(442): WP_REST_Server->dispatch()

#9 /home/ssidoors/prodato.rs/wp-includes/rest-api.php(410): WP_REST_Server->serve_request()

#10 /home/ssidoors/prodato.rs/wp-includes/class-wp-hook.php(308): rest_api_loaded()

#11 /home/ssidoors/prodato.rs/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()

#12 /home/ssidoors/prodato.rs/wp-includes/plugin.php(565): WP_Hook->do_action()

#13 /home/ssidoors/prodato.rs/wp-includes/class-wp.php(399): do_action_ref_array()

#14 /home/ssidoors/prodato.rs/wp-includes/class-wp.php(780): WP->parse_request()

#15 /home/ssidoors/prodato.rs/wp-includes/functions.php(1332): WP->main()

#16 /home/ssidoors/prodato.rs/wp-blog-header.php(16): wp()

#17 /home/ssidoors/prodato.rs/index.php(17): require('/home/ssidoors/...')

#18 {main}

now we contacted Automattic as we received the in the following modules the errors.

The errors we receive in 

WooCommerce – orders, 

WooCommerce – Customers 

products-  all products 

products- categories

Analytics?– products

all these modules where not showing up and having fatal errors and this debugging as youo can see from the dates on we started the debugging part. When the WP version was set to ENG language all worked 100% when set to SR we got these problems.

Now the standard debugging part turn of plugins turn on etc etc where done by Automattic themselves to figure out the issue. In the end we noticed that in loco there was a issue. Now we had previous set up a custom language as we did needed Serbian Latin script which we translated by hand this maybe we did somethign wrong in it or what the issue in here was we actually do not know.

What i did then was to copy the translation in the original language which the site was set to and all started to work. The custom file was deleted and now simply it does work. Again this sis the short version as you can see from the 16th of march we were trying to figure out what and how.

That why this issue was pretty interesting and the boys and girls from automattic were very helpfull. We pinpointed it only to loco and you have seen the message i copied to you. When i reinstalled it and did the langauge copy all worked again without a glitch.

If you want to browse to the full error log and the system files just let me know i can email them to you.

Cheers

Dragan

Hi Tim,

We finally found the issue and resolved it successfully.

The issue we used a custom translation which ends in?sr, while they should be?sr_RS not sure how we missed this all however we changed this into the correct sr_RS the issues where not there anymore.

Not sure what and how but this caused the fatal error as we used the same translation made a new copy into the correct format and it’s simply worked.

Why it’s clashing probably we will never know but it simply works after a few hours of testing so we do kot ask further.

Cheers

Dragan

Ajd da se ne radujemo pre rano evo jutros je WP dao vulnabirity i security issues warning i sve pluginove (youst, woocommerce, elementor, elementor pro itd) izdali su nove verzije svog plugin.

https://patchstack.com/database/vulnerability/wordpress/wordpress-6-1-1-unauth-blind-ssrf-vulnerability?_a_id=110

Samim time jos WP sam nije izdao novi updejt… Ocekujem stime problme jel je ovo server side problem…

Sve radi kako treba nemamo ni jedan problem vi?e…

@ivijanstefan

Ajd ovako od nedelje ja cu da postavim jedan staging sajt od naseg orginala, i sve sta mi koristimo itd. Ako zelis dajem je direktan pristup staging sajt pa se ti malo tu igraj da vidis sta i kako.

Mi sada i live enviroment nazalost krecemo posle ovog vikenda i za sada necemo da ukljucimo tu opciju ali na staging sajtu mozes da testiras te probleme jel ipak znas vise od nas o tome. Mozda ces ti nesta da vidis sta mi za sada ne vidimo.

ako zelis tako nesta slobodne se javi na moj mail dragan at prodato tacka rs pa se cujemo. Nadam se da mozemo vama isto pomoci sa ovim.

Pozdrav,

Dragan

@ivijanstefan

evo danas smo morali da isklju?imo AJAX elementa iz va?eg plugin jel je nije radio ajax element u tome. Korpa je zabugovala i posle toga cak i check out nije bio pristupan uvek samo vrti. Kad smo tu opciju na novu verziju isklju?ili onda je sve proradilo.

Tako?er se pojavili neke PHP gre?ke tokom tog uklju?enje. Fatal error call tu function, warning, class wp fatal error itd sada ?emo da pratimo ostalo pa ?emo da vidimo ?ta se de?ava.

@ivijanstefan

verzija 1.8.6 izgleda da radi na sajtu dobro. Postavljena je jucer kakd je plugin izasao i aktivaran je AJAX komp.

Za sada imamo samo neki warning array to string conversion ali to izgleda da litespeed nesta sada upisuje sto je cudno ali ostalo radi kako treba ne vidimo problem za sada.

pozdrav,