Forum Replies Created
-
Posts
-
Hi Josue – just back in the office and i checked it again – strangely it’s working fine now! i have no idea what was happening before, but i tried multiple times previously with different images, and they all gave me that “line 360” error.
anyway, i guess you can close this one. thank you!
hi andy – as noted in the update, it went away after i re-added elements to the page. it was very strange! thanks for checking in.
well, i think we’ve figured it out, josue; it was a plugin conflict with one minor element of one plugin: ignitewoo’s automatic cart discount. deactivated, and all better. thanks again for all your help. you were huge, sticking in there with us. very much appreciated!
Further info from Woo:
Hi Jim,
The issue is definitely theme related as the theme is using
chosenwhich is what Checkout Field Editor is also attempting to use. See http://cld.wthms.co/JYYZ. Switching to a default theme such as Twenty Fifteen would solve this for example.I’m not sure how we could proceed here. Is there anything the Enfold developers can provide to disable or remove
chosenfor that page? Checkout Field Editor needs it for that page.So their analysis shows that the Enfold theme and the Checkout Fields Editor plugin are conflicting over this
chosencommand. What can we do?thanks, yigit! that worked perfectly for hiding the numeral.
so a numeral counter is now part of Enfold for the cart icon? why does it show “zero” then when there’s something in it?
i updated, still the same issue. i am unable to update the Checkout Fields Editor to the new version (1.3.0) from the current (1.2.11). i have asked Pagely (the hosting company) to look into it, and i’ve also asked Woo to look into it. I’ll keep you posted, Josue. thank you for your help. much appreciated.
josue: in the backend, when you go to add a new field or even modify existing fields. it’s like it’s locked – i can’t do anything with it anymore. i installed the new Enfold update but no change, as Andy thought might be the case.
hi Andy – we’ve already done this with the support team at WooCommerce. that’s when they identified the error as coming from the Enfold theme, which is why i brought it to you all. glad to hear there will be a theme fix for this soon. i appreciate everything Kriesi does to keep Enfold the best it can be! i use it everywhere!
the issue began relatively recently, i believe after an update to Enfold. according to the woo people, from the message above, they believe it’s a JS error coming from Enfold, a minor one but enough to keep the plugin from working properly.
thanks for looking into it. i really appreciate it.
thank you, josue! that fixed the problem. what a strange issue, too. i’ve never seen it before on any responsive implementation of Enfold, but then, i don’t often use portfolio items, either.
my problem was the product search plugin from woocommerce – it breaks the new version. i disabled it and everything works. hopefully they get a fix soon!
rikard – my hosting company Pagely rolled back WooCommerce to the previous version – 2.27 from 2.3.3 – because there’s something wrong with the update. it not only caused that plus-minus button issue, but caused some pages to not render properly as well.
thanks for checking!
elliot – what do you mean, add it “in the page”? to the index.php file?
how about using the custom CSS? i prefer that, as it survives updates to the theme.
i added this part:
.av_one_fifth span { margin: 0 4px !important;to custom CSS, it seems to still not be centering anything.
Elliott – that’s awesome, the code worked perfectly. how on earth would that “hidden” class get there? i didn’t add it to custom CSS…
thanks again for your help – happy holidays!
thanks, Andy – yes, i have it set to display in HD on embed. my point is that the fullscreen slider doesn’t use embed code – it uses a link to the video. it seems that in doing this, it defaults to a lower-resolution playback. that was my point earlier.
thanks for the help!
