adopted3
Forum Replies Created
-
Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeNot sure if these errors could relate:
Fri Jul 23 14:04:30 GMT-700 2021 ru.cdev.xnext.client.UncaughtExceptionHandler SEVERE: undefined java.util.ConcurrentModificationException ru.cdev.xnext.legacyfrontendstub.LegacyFrontendStub-0.js:2555:158 Uncaught Error: java.util.ConcurrentModificationExceptionForum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeYeah, it still often doesn’t load the slider. (Firefox only) đ
Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeI went through all our slides, and our first slide had a background image (not found) in the “Content â˘â˘â˘” section, in addition to the background image in the “Slider â˘â˘â˘” section.
I deleted the reference to the background image in the “Content” of the first slide shown.
Could that have prevented the slider from loading? It’s loading now, but I’ll need some time before I know, because it has been intermittent.
Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeI spoke too soon– the problem must be intermittent. Slider not showing on page with Ecwid code.
I’m seeing an “unreachable code after return statement” in the Ecwid script.js.
Also, sometimes a failed GET for an image (not found)… but I’m not using that image anywhere, and wondering if it’s still stuck in my slider.Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeHi @laszloszalvak ,
An update for you: I’ve tested WP 5.8 with the Twenty Twenty-One theme, and there is no conflict with the Ecwid plugin… all’s well.
Thanks for your help!
Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeThanks for the helpful info.
I disabled Autoptimize and Cloudflare cache, cleared browser cache, and the problem still existed (slider not showing).
When I re-activated the Cloudflare cache and Autoptimize plugin, I also updated the “Really Simple SSL pro” plugin to Version 5.0.
At that point, the test page worked for me in Firefox. I’m not sure if it was purging the caches (I had done that before), the update to the SSL plugin, or randomly worked, but since it worked, I re-enabled the Ecwid plugin, and got the store set up again, but was getting this error where the slider belongs on front page: “Notice: Trying to access array offset on value of type null in /home/bigbstr2/public_html/wp-content/plugins/smart-slider-3/Nextend/Framework/Model/Section.php on line 57”
I’ve disabled the slider on the front page, to keep the store working. I also turned WP_DEBUG off.
We’re planning a new website, so I probably won’t spend much more time on this, although I might try switching to a different default WP theme.
Thanks again!
PaulForum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeThanks again for your prompt reply.
I’ve found that the test page works in the Chromium browser, but not in Firefox (on my PCs so far).
The Chromium console shows a couple errors that the Firefox console doesn’t show. However, I removed any that Chromium also noticed, so here are the errors I see in Firefox (where it’s broken), but not Chromium (where it works):
NOTE: the script.js referred to here is Ecwid’s https://app.ecwid.com/script.js
I will share this with the Ecwid tech support:unreachable code after return statement script.js:1356
unreachable code after return statement script.js:1624:1
The script from âhttps://d2scn539ulxr09.cloudfront.net/rosetta/translations/new-frontend/files/new-frontend.en.507559234.jsâ was loaded even though its MIME type (âtext/htmlâ) is not a valid JavaScript MIME type. test-ecwid-smart-slider-3-conflict
unreachable code after return statement script.js:1356
unreachable code after return statement 2 script.js:1624:1
unreachable code after return statement script.js:1356
unreachable code after return statement script.js:1624:1
JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709
Some cookies are misusing the recommended âSameSiteâ attribute 28
Request to access cookie or storage on â<URL>â was blocked because it came from a tracker and content blocking is enabled. 11
This page uses the non standard property âzoomâ. Consider using calc() in the relevant property values, or using âtransformâ along with âtransform-origin: 0 0â. test-ecwid-smart-slider-3-conflict
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
Some cookies are misusing the recommended âSameSiteâ attribute 3
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring â’unsafe-inline’â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttps:â within script-src: âstrict-dynamicâ specified
Content Security Policy: Ignoring âhttp:â within script-src: âstrict-dynamicâ specified
HorizontalCategoriesWidgetV2 loaded ru.cdev.xnext.legacyfrontendstub.LegacyFrontendStub-0.js:1114:53
The script from âhttps://s3.amazonaws.com/yotpo-plugins/ecwid/config/877073.jsâ was loaded even though its MIME type (âapplication/jsonâ) is not a valid JavaScript MIME type. test-ecwid-smart-slider-3-conflict
Use of Mutation Events is deprecated. Use MutationObserver instead. rocket-loader.min.js:1:9496Regards,
PaulForum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeI just disabled all plugins except Smart Slider. (I’m not using the Ecwid plugin, just the direct embed code.)
The problem is the same, except that this time in place of the missing slider is the text “Notice: Trying to access array offset on value of type null in /home/bigbstr2/public_html/wp-content/plugins/smart-slider-3/Nextend/Framework/Model/Section.php on line 57”.
(Sorry, I need to keep the other plugins active now.)
Forum: Plugins
In reply to: [Smart Slider 3] Smart Slider 3 conflict with Ecwid plugin or embed codeHi @nextend_ramona , thank you for your reply.
I set up a page demonstrating the problem here: https://bigbeartools.com/test-ecwid-smart-slider-3-conflict/
I’ve turned on WP debugging, but for some reason I’m not seeing the error I mentioned above (in debug mode, WordPress was putting the error message about Section.php line 57 right where the slider would be.
I still have this problem when Smart Slider and Ecwid are the only active plugins, but I will test again just now to be sure.
Let me know if you spot anything, and thanks again for your help.
PaulForum: Themes and Templates
In reply to: [Twenty Nineteen] Custom CCS – Remove Header in Twenty NineteenYes, that advised code would definitely make your site vanish:
.site-content { overflow: hidden; display: none; }If you’re trying to hide the logo, title, etc at the top, use @john-alexander’s code:
.site-branding-container { overflow: hidden; display: none; }If you’re trying to hide the title and whitespace underneath the site branding/menu/etc., try this:
.entry .entry-header { overflow: hidden; display: none; }Neither answered the question. I think OP was asking about the title area on a page, not so much the site branding area above it.
For the title area, remove it and the whitespace with this:
/* remove giant twentynineteen title */ .entry .entry-header { overflow: hidden; display: none; }Great, thank you!
Thank you
Forum: Fixing WordPress
In reply to: Upgrade stalls at ‘unpacking the update’Like @mworleysr, I deactivated all plugins, then clicked the re-install WordPress 5.0.1 button. I finally saw the WordPress 5.0 Welcome Screen.
I figured out the problem… it was my adware blocking browser plugin (“Disconnect”).