Forum Replies Created
-
Posts
-
yes, but has the last version of Enfold changed the css of WooCommerce?
Hello ismael,
thanks for support.It is grey because I have overridden with my custom css.
I only would like to know if the property border-color #ffffff is set from the new version of Enfold for some reason.thanks
Hello Nikko,
it is not working.I fixed by myself some css, but the product box (as you can see from the link) have still issue.
This problem it is happening only to me or also to all other Enfold with WooCommerce installed?thanks
Now I override them with my css, but this is not a solution because probably there are more that I still not find:
#top .main_color .input-text, #top .main_color input[type=’text’], #top .main_color input[type=’input’],
#top .main_color input[type=’password’], #top .main_color input[type=’email’], #top .main_color input[type=’number’],
#top .main_color input[type=’url’], #top .main_color input[type=’tel’], #top .main_color input[type=’search’],
#top .main_color textarea, #top .main_color select, #top .select2-search input[type=’text’],
.main_color table, .main_color th, .main_color td, .main_color tbody, .main_color tfoot, .main_color thead,
.main_color div#payment { border-color: #e1e1e1; }
.main_color #payment li { background-color: #f2f2f2; }it looks like was the file woocommerce-mod.css that set to border white to a lot of things. Is that possible?
thanksHello Ismael,
I’ve just updated Enfold to the 4.1.2 version.
I have also deleted from my child theme the code for the Schema you posted.Now, if you test the product page with the Google Structured Data Testing Tool, you can see there is still an error (see the link in the private content).
It says “is not a known valid target type for the identifier property”.Thanks for support
Hi Rikard,
I’ve just update WooCommerce to the last release (3.1.1), but the problem still persist.
I’ve found that if I insert the URL of the Vimeo video with the http protocol instead of the https, the problem doesn’t show up.
Hope it helps.Thanks
Ok, we will wait the release of WooCommerce 3.1.1 and we will see.
ThanksThe code that Ismael give us make a fatal error!
$this->set_data at line 24, we are no in object context.
Can not use $this if you are not inside a class.thanks
Hello,
I found an error in the Ismael code.
Where there is $this->set_data at line 24, we are no in object context.
This will cause a fatal error.Thanks
Hello Andy,
it is related to the thread, because the structured data are generated from the code that Ismael wrote.
And about Yoast SEO, it has nothing to do about the WooCommerce Product structured data.
So please let me know about my question,
thanksHello guys,
sorry to disturb again, but is it correct to have in my search console all the structured data with “Markup: schema.org”, instead for the products are “Markup: mydomain.com”
Of course mydomain is an example… there it goes the domain of the site I installed your code above.
Thanks for support
Sorry Basilis,
my bad… I completely screw up.
I’ve just debugged line by line. The code responsible for that was another that hooks into the pre_get_posts.
Really sorry again and thanks for being so gentle.Hello Ismael,
the hook you give us breaks the functionality of the search tool in the WooCommerce > Orders page.
It breaks both the filter and the search.I don’t really know why, but this is.
Do you have any idea because of what?
thanks
Now I am testing with the last new release of WooCommerce 3.0.5.
The product page is ok.
I don’t know with the product gallery images, because I don’t have it on my website.
Let you know if I find something else.
ThanksHello Victoria,
the main issue was that the product page, made with the builder, didn’t show up.
I mean, it arrives at the page with the correct URL, but then all the content were not returned.We had to use a backup to recover the older version.
Thanks
Hello Ismael,
I have a lot of errors, do you?
Fatal error: Uncaught Error: Call to undefined method WC_Product_Simple::get_name()
Stack trace: …
…I know it, but you are talking about the microdata markup on the single element.
I am talking about the <script type=”application/ld+json”> that is in the <head>.With layout builder > no json
Without layout builder > yes jsonIn my opinion the layout builder disable some function that is responsible for the output of the json LD for products.
Sorry Ismael,
I think you are wrong.I’ve just tested a new WordPress installation with Enfold and WooCommerce only, not other plugins installed.
If on the product page I am not using the layout builder, in the html page there is the correct output of the json<script type="application/ld+json">{"@graph":[{"@context":"http:\/\/schema.org\/","@type":"Product","@id":"http:\/\/localhost\/wordpress\/prodotto\/flying-ninja\/","url":"http:\/\/localhost\/wordpress\/prodotto\/flying-ninja.... .....Instead using the layout builder there is no the <script type=”application/ld+json”>.
Is this a bug?thank you for support
