[tylerParticipant]

About errors linked to the “alt” attribute to images:

if I’m writing down an alt text for an image it says than that the changes are saved. But it’s not and also with the inspector>properties I can see the alt text missing.

I’ve seen this problem also while editing the images: only if I upload a new image ti will be affected by changes; an already published image won’t have any change from editing or insert/modify the property fields (like name and alt).

Add New Note to this Reply

[tylerParticipant]

this one also is generated from TheCreator (while placing a youtube element inside a section):

Error: The frameborder attribute on the iframe element is obsolete. Use CSS instead.
From line 1916, column 49; to line 1916, column 243
e .video”><iframe src=”http://www.youtube.com/embed/CqDs08vCwPk?autoplay=0&modestbranding=0&controls=1&fs=1&start=&end=&showinfo=0&rel=0″ frameborder=”0″ allowfullscreen>

(sorry for multiple posting, I just imagine is more helpful to youhaving all the errors listed here instead of go through the validator’s output!)

Add New Note to this Reply

[tylerParticipant]

Oh, and i see there are a lot of both warnings and errors about the attribute “;” which is not allowed or not serializable. Again, I think is automatically generated from the site builder or theme itself. Can you please give me a feedback also for that?

thanks!

Add New Note to this Reply

[tylerParticipant]

Hi and thx for the quick answer.

about the warnings, it’s not a big issue – I know that is preferred to have headings , also is more SEO friendly. What’s concerning me more are the errors.

It seems that some errors, like this one:

Error: Element p not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
From line 1584, column 1; to line 1584, column 44
><span>↩<p class=”p_tc” style=”text-align: center;”><span

are generated while creating a new section with TheCreator (included in Jomelle) and there’s a misuse of element <span> (errors nr. 4, 6, 9, 15, 22 …) – or at least is what the validator is telling.

or this one:

Attribute ” not allowed on element a at this point.
From line 1737, column 98; to line 1737, column 175
/span> //

which is from an AB included plugin and it seems to be just a missing target condition (so bad to be a problem for the validator?).

Do you think the patch coming with the next update will fix these problems?

Thanks a lot

Add New Note to this Reply

[tylerParticipant]

Ok, I understand. Thanks in any case for the fast answer. Greets.

Add New Note to this Reply

[tylerParticipant]

pls try now

Add New Note to this Reply

[tylerParticipant]

Hi, thanks for the answer, but I cannot see any difference from the situation before.

anytime I re-open the popupmaker settings, they appears all as defaults one and I’ve to re-set anytime ALL the settings if I want to modify something inside the popup.

The only setting that seems to be saved is the Fixed Postioning: if the box is checked, it will stay as it is also if I update/re-open the setting page.

The problem is not that the JetztTesten button isn’t working, the problem is that I’ve to re-set any single setting in the popupmaker backend page due to a conflict with AB Testimonials …

Add New Note to this Reply

[tylerParticipant]

Hi,

Below the staging site (where the problem is the same).

I’m using popup maker to trigger a registration form from a button (the “JETZT TESTEN” one in the bottom of the page).

Thanks

Add New Note to this Reply

[tylerParticipant]

Problem is that PopupMaker settings are erased anytime I update the popup, also without making any change (so anytime I open again the same popup it shows ALL settings as default ones). The plugin’s support told me to deactivate all plugins and re-activate one by one to check if there’s any conflict with one of them.
After deactivating AB Testimonials the problem disappeared.

There’s an error in the console: “util.js:30 Google Maps API warning: SensorNotRequired: https://developers.google.com/maps/documentation/javascript/error-messages” but I doubt is connected with this plugin’s issue..or?

Hope these info could help

Add New Note to this Reply

[tylerParticipant]

Situation is partially solved now; I gave to the coder the not-imported custom css from old site and he included it. Now 90% of the customization is back. The Creator is still not working properly (please try to go on a random page and try to use the “text box” inside a section; no text area -including format options- will be displayed)

Add New Note to this Reply

[Author]

Posts