Hi @vicnicksor,
We have no validation issue on our demo site. Can you please share your site URL so that we can take a look into it.
Thanks,
Hi, @mohsinrafique,
This is because your demo site does not use tables with the <colgroup> tag.
Your colleagues have the following decision, if I am not mistaken:
'col' => array(
array(
'attr_spec_list' => array(
'span' => array(),
),
'tag_spec' => array(),
),
),
'colgroup' => array(
array(
'attr_spec_list' => array(
'span' => array(),
),
'tag_spec' => array(),
),
in file accelerated-mobile-pages\includes\vendor\amp\includes\sanitizers\class-amp-allowed-tags-generated.php.
I would not like to give links to my site here, but here is a link to a screen shot with a validation error.
Thank you for your prompt reply! 🙂
The plugin has been updated, but the bug has not been fixed. For a whole month, the developers have not done anything in this direction.
It is very unpleasant for me, but I have to give up this plugin in favor of the one that really works and where developers listen to users.
Hi @vicnicksor,
Sorry to hear about your experience.
The support for colgroup is already added in our previous versions of AMP WP. But ‘width’ attribute is not supported in HTML5 template.
So there is no problem at all regarding ‘colgroup’ in AMP WP plugin. For your reference/knowledge, see the link
Also we have a lot of other tasks in pipeline which are on top of the list and we need to entertain them first before to look into any new requirement/feature.
So your 1 rating for us is unfair.
I’m just stunned by this answer. o.O
Backward compatibility support is the responsibility of a competent developer. Your excuses are inappropriate and ridiculous.
And considering this your comment, my assessment is more than fair.
Hi @vicnicksor,
I think there’s been a misunderstanding here. AMP itself doesn’t support this and gives validation errors.
Please see this screenshot.
There’s nothing we can develop on our end to provide support for this as AMP itself doesn’t provide backward compatibility for this. If there was a way around this we would love to fix it but it’s out of our control.
Hope this clarifies it.
Thanks
o.O
Um, are you really a programmer?
I ask this because even I managed to solve this problem for your plugin using regular expressions. Naturally, after the update my patch disappeared. And when I realized that the error you have not fixed, I just removed your plugin.
And now I’m starting to think it’s because you just don’t understand how it can be done
I indicated above in what file and how this problem was solved at your colleagues. Study their code.
Learn PHP and learn how to program, after all. Because your answers give you away.
