Forum Replies Created
-
Posts
-
We found out that it was the https://de.wordpress.org/plugins/wp-typography/ plugin which struggles, because the html markup of the content builder isn’t clean in the frontend.
we switched it of and it now works, but is that the solution?
@Rikard
Please test it locally on your testing enviroment and also you can test it on the site you already know see below. it doesnt matter.
in any enviroment it doenst save the page.Apart from that, we have another bug since friday on the same site si***.com where we lost the second half of the page. after updating some content.
Why could that happen?link is below.
@Rikard please try the link again!
As you can see in the demo video we save the page but after saving the page the html structure changes, so that the footer is not in the #wrap_all container anymore. this is what we can replicate (see the demo video).
there is an issue with the avia editor for sure. because if we remove a space between to shotcodes it works again. after updating something again in the avia editor the error appears again.
an extension on that topic:
we also recoginzed that sometimes enfold updates the page but not the avia editor in the backen (which jumps back to the version before), changes in the frontend are seen but after updating the avia editor again, the changes of the last frontend version are gone again. This doesnt appear if i use the classic editor instead for changing the content. I think the avia editor doent load the latest version of the page in all cases.This extension on the issue also appears on a completly different environment here:
from time to time clients complain about that issue. which happens on several sites.
Although my the issue seems to be specific. It isnt!
This seems to be the same bug as https://kriesi.at/support/topic/avia-editor-bug-with-footer/As you can see in the description we have the same result there. And I think that we are not alone.
Clients override their changes…over and over again by this bug. which is pretty urgent now. We get lots of complaints
Hi Rikard,
thanks!
I found it. in that page we used an emoji (“😊”) this was blocking the page from updating.
Why? i don’t know, but maybe you can tell me..? does it work on your end?
@Nikko could you please share your fixing code?
Maybe it would help me.Thanks
The video is muted of course. Could you please give me the your browser specification so i can replicate the autoplay.
i tried mutliple browsers and it didn’t work.
But this comment helped:
https://stackoverflow.com/a/50213665You need to set both parameters like this example to make it work:
https://www.youtube.com/embed/xY2W1As-Plo?mute=1;autoplay=1Hi,
The Screencast I made is on normal desktop on an iMac.
So there should be autoplay working.
What’s wrong?Ok. Issue solved. it was a custom cookie (aviaPrivacyVideoEmbedsDisabled) set by enfold-child to stop videos.
you can close the issue thanks
@Ismael i added a topic: https://kriesi.at/support/topic/color-section-background-video-not-working-2/
as you requested. thanks!
@Ismael Just a quick reminder. What’s the status here?
Hi Günter,
ich habe noch nichts von dir gehört.
Könntest du Kriesi noch meinen Github Username durchgeben,
damit er mich hinzufügen kann, ich hätte wirklich ein paar spannende Pull requests.
Danke dir!
DavidHi,
the page still uses a “core”-fix. because i really cant get your script to work in my testing environment. are you sure it works? did you test it with a local mp4 file?
thanks!
Thanks @Günter
Can you ask Kriesi giving me access to make pull requests to Kriesi directly too?
Would be much faster a lot of fixes and adding a couple of missing hooks in the core!Thanks a lot!
Hi Ismael,
thanks for that workarround but fullscreen-icon is now available. but playing the video is not working anymore.
is there no options filter for the media player?! the script looks pretty big.thank you very much!
Hey @Dude
any update on this issue so far?thanks!
Thanks @Ismael!
If i re-initialize.avia-video. i get two control bars: https://d.pr/i/K3BhXs
I only would like to add “fullscreen” feature for.avia-video@Dude Wurde dieser Bug in 4.4.1 bereits behoben? Wenn nicht bis wann?
wäre schön, wenn man nur einmal patchen müsste und nicht bei jedem Update erneut.Vielen Dank!
Do you have the chance to replicate the bug via https://www.browserstack.com/ because it definitly isnt loading! on Mac OSX in Safari 11
