Bug mit Modern Polls + Customizer

  • Resolved wegerl

    (@wegerl)


    4 years, 8 months ago

    …the moment a bug! – in activation of the plug-in the Customizer > ‘Additional CSS’ is broken. I.e. After saving the code and closing the customizer, the adjustment is not there. Next time you open the customizer, you can see that the codes are faulty. This is different if CSS is already saved before. The CSS code that was already there before is not changed, but the new code is not saved.

    So you can use the plugin and the “Additional CSS” to deactivate the Modern Polls. After that the Customizer works and CSS code can be saved without errors. When the poll is activated, this remains the same.

    I tested on wegerl.at with WordPress, ditmars.bplaced.net with ClassicPress (…and they say to the website, this is good input) and on MAMP.

    So maybe for the next update! – so that it is a poll as it is in design, handling and then also to the function simply only performer.

    And hello! – and above all, thank you very much for the plug-in Modern Polls.

    … und auf gut Deutsch:

    Des Moments ein Bug! – in Aktivierung des Plug-ins ist dann der Customizer > ‘Zus?tzliches CSS’ defekt. D. h. Nach abspeichern des Codes und schlie?en des Customizers ist die Anpassung nicht da. N?chst dem ?ffnen des Customizers ist zu sehen, dass die Codes fehlerhaft sind. Anders wenn schon vorher CSS abgespeichert ist. Da wird zwar der schon vorher da gewesene CSS-Code nicht ver?ndert, aber dem nun neuen Code folgt keine Abspeicherung.

    So bleibt in Benützung des Plug-ins und des “Zus?tzlichen CSS” die Deaktivierung des Modern Polls. Danach funkt der Customizer und CSS-Code sind fehlerfrei abzuspeichern. In Aktivierung des Polls bleibt dies dann auch so erhalten.

    Getestet wurde von mir auf wegerl.at mit WordPress, ditmars.bplaced.net mit ClassicPress (…und man sagt zur Website, das ist guter Input) und am MAMP.

    Also evtl. für das n?chst Update! – sodass es ein Poll wie es in Design, der Handhabung und dann auch zur Funktion einfach nur Performant ist.

    Und hallo! – und vor allem Dir vielen Dank für das Plug-in Modern Polls.

    Ditmar?

    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
    • This topic was modified 4 years, 8 months ago by wegerl.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter wegerl

    (@wegerl)

    Edit: This is different if CSS is already saved before. The CSS code that was already there before is not changed, but the new code is not saved.

    Bearbeitet: Anders wenn schon vorher CSS abgespeichert ist. Da wird zwar der schon vorher da gewesene CSS-Code nicht ver?ndert, aber dem nun neuen Code folgt keine Abspeicherung.

    The class FelixTzWPModernPollsApp should be plugged into an instance and then loaded using the plugins_loaded hook.

    This way WordPress itself can control how something is loaded. But if the class is set directly in the plugin file, this causes problems with internal features of WordPress. So also with the CSS-Editor.

    Unfortunately the plugin is broken, unless this is fixed.

    Plugin Author felixtz

    (@felixtz)

    Sorry that you had to wait for so long, i had been to the hospital (but not because of the current situation).

    Nevertheless, this Error/Issue has now been fixed (in 1.0.5).
    And thanks to @pixelbart ‘s suggestion.

    @felixtz

    Well, get well soon and thank you for your feedback.

    I’m glad it worked out. Stay healthy, or at least try!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Bug mit Modern Polls + Customizer’ is closed to new replies.