Miguel

It is a browser cache issue. Open Dev Tools and enable “Disable cache”. Now it works. We are adding to cart through popup on same page, the AJAX way, I guess.

• This reply was modified 8 months, 4 weeks ago by Miguel.

Same issue. Cart is not editable. But it is fixed by opening Dev Tools and disabling cache.

I can confirm too. Great job.

Stack trace:
#0 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-post-element.php(54): SitePress->is_display_as_translated_post_type()
#1 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(445): WPML_Post_Element->is_display_as_translated()
#2 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(238): WPML_URL_Filters->is_display_as_translated_mode()
#3 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(310): WPML_URL_Filters->permalink_filter()
#4 /opt/bitnami/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#5 /opt/bitnami/wordpress/wp-includes/link-template.php(371): apply_filters()
#6 /opt/bitnami/wordpress/wp-includes/link-template.php(201): get_post_permalink()
#7 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1099): get_permalink()
#8 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths()
#9 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(357): Google\Site_Kit\Core\Assets\Assets->get_inline_base_data()
#10 [internal function]: Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}()
#11 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Script_Data.php(51): call_user_func()
#12 [internal function]: Google\Site_Kit\Core\Assets\Script_Data->Google\Site_Kit\Core\Assets\{closure}()
#13 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func()
#14 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print()
#15 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#16 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#17 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#18 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(156): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#19 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}()
#20 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#21 /opt/bitnami/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
#22 /opt/bitnami/wordpress/wp-admin/admin-header.php(146): do_action()
#23 /opt/bitnami/wordpress/wp-admin/index.php(137): require_once('...')
#24 {main}
 thrown in /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3937

Still the same. It did not fix the issue. I set the product option to “Translatable – only show translated items“ then activated Google plugin and boom… site went down. Sorry and thanks, @jamesosborne

• This reply was modified 1 year, 3 months ago by Miguel.

Thanks, @jamesosborne . It happens with Site Kit by Google 1.106.0 and WPML Multilingual CMS 4.6.4.

I had Site Kit by Google 1.105.0 and WPML Multilingual CMS 4.6.4 and everything worked fine.
JFYK.

Same situation. It looks it is trying to get a value from a non-existing array key/position.

Only happens when you are a logged in admin.

• This reply was modified 1 year, 3 months ago by Miguel.

This looks like a security regression (CVE-2018-6389), I mean, a closed vulnerability reopened in the future. It is a serious issue, and should be patched as soon as possible. Adding define( ‘CONCATENATE_SCRIPTS’, false ); did not work to me.

I think the WP Core Team should patch it as they did in the past.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6389

That’s great, @cssultan . I found that column on the wp_mint_contacts table. But, it would be even greater if the shortcode “preferences_page” detects that the user is already logged in and automagically, it loads that hash.
Currently, the only way to get that preference page is via email link, and that’s not good enough for a complete customer satisfaction. Users should be able to change newsletter preferences right from the WP Mint Mail Preferences page.

Thanks again.

Miguel

Hello, @cssultan and thank you for your time.

We go straight to the Mint Mail Preferences page by writing its URL in an active user session. Does it take any kind of hash to display user preferences? In that case: how can we get that hash to compose a link from a logged in user? Any shortcode?

Thanks again.

• This reply was modified 1 year, 6 months ago by Miguel.

I deployed this plugin on two WP instances. Same behavior. No cache plugin. Versions 1.2.4 and 1.2.5. Shortcode preference_page is present and template is Preference page too.

• This reply was modified 1 year, 6 months ago by Miguel.
• This reply was modified 1 year, 6 months ago by Miguel.