undefined functions have nothing to do with sites being live.Quote:
Originally Posted by CandleMan
split was deprecated in php 5.3 and removed in php 7.0. you can see some alternatives here:
http://php.net/manual/en/function.split.php
best.
Printable View
undefined functions have nothing to do with sites being live.Quote:
Originally Posted by CandleMan
split was deprecated in php 5.3 and removed in php 7.0. you can see some alternatives here:
http://php.net/manual/en/function.split.php
best.
It seems the rules for the description field in the Google Merchant Centre Product Search Feed have been changed recently by Google. I'm suddenly getting 'Unsupported HTML tags [description]' warnings from Google which suggest I need to remove any unsupported HTML tags from the rich text attribute values.
See https://support.google.com/merchants/answer/6324468
In my case it mostly seems I have...
and it would seem Google now wants...Code:&
Code:&
So I went through my Zen Cart descriptions and fixed the problems ones to use the HTML entity, but Google still gives the warnings.
Obviously it's a bit more complicated than I first thought. Even if I've put the right HTML entity in the Zen Cart description...
[CODE]<p>The Light & Motion GoBe/Sola Universal Hand Strap is just what you need if you're looking for hands free use of you Light and Motion GoBe/Sola lights.</p>[CODE]
It's written by the Numinix Google Product Search Feeder add-on into the feed XML file as...
Code:<description><![CDATA[The Light & Motion GoBe/Sola Universal Hand Strap is just what you need if you're looking for hands free use of you Light and Motion GoBe/Sola lights. ]]></description>
Google has decided this is wrong. But what is the solution?
Did you try replacing & with "and"?
Yes, and that works. But the problem if that some brands use & in their name, e.g. Light & Motion, Sea & Sea. Thus people search for them using & not and. So in descriptions I will typically use the name both ways to be user and SEO friendly.
A lot of free services have their limitations.
True enough. After some more digging, as best as I can tell using CDATA this way for ampersand characters is the right thing to do by the XML spec. But Google have obviously changed some checking and are now incorrectly flagging this as a problem.Quote:
Originally Posted by marton_1
i have done some digging as well.... there are many others with this problem:Quote:
Originally Posted by lloyd_borrett
https://www.en.advertisercommunity.c...d/21523/page/1
i have also looked at the XML spec. it is indeed correct that withing a CDATA section, you can use an non-escaped ampersand:
"Within a CDATA section, only the CDEnd string is recognized as markup, so that left angle brackets and ampersands may occur in their literal form; they need not (and cannot) be escaped using " < " and " & ". CDATA sections cannot nest."
in addition, this situation is a WARNING, not an error. in fact, i am seeing the same thing in one of my clients feeds.
bottom line, i would not change a thing, but i would monitor the feedback from google to see if they start banning your products.
finally, php 5.3.29 is WAY old, and not at all certified to be compliant with ZC 1.5.5. how can your site possible be working? or is your signature wrong?
best.
Signature is correct. I have a lat9 to keep it going, who does an amazing job. Sadly there is another system running on the site that needs the older version of PHP. It needs replacing.Quote:
Originally Posted by carlwhat
I have my shop in 3 languages and have attribute color. The XML extracts always give the <g:color> in the Dutch language (my primary language). What do i need to do to get it in the correct language? In the configuration I changed the language to Germand and switch the ADMIN to german. Everything is in German except the color attribute. please help me.
A few days later Google stopped flagging this as a problem.Quote:
Originally Posted by lloyd_borrett