[2.0.0beta2] serendipity_event_freetag

[u1amo01]

Hi,
I have serendipity_event_freetag Vers. 3.50 installed. In the frontend every thing looks good. In the backend I can't see were to add tags to an entry?

Below the field for the text there are two buttons "Entry metadata" and "Advanced Options". When I click on them nothing happens.

I use Iseweasel 24.4.0 as Browser. Deactivated my Adblock Plus, but it didn't help.

[MarioH]

In my testblog, the tags are under "Erweiterte Optionen" at the end of the article page.

Greets
Mario

[onli]

Below the field for the text there are two buttons "Entry metadata" and "Advanced Options". When I click on them nothing happens.

The fields should open, and the tags be under "Advanced Options". Is Javascript enabled? Can you open Seaweasels Console and check the error message that should be produced when clicking on the button?

[yellowled]

In my testblog, the tags are under "Erweiterte Optionen" at the end of the article page.

Same here, although I'm not on 2.0-beta2 (but on a recent GitHub checkout). That is, BTW, the place where tags used to be in 1.7.

The buttons not expanding the correspoding areas does worry me more. What was Iceweasel again, some kind of unbranded Firefox?

YL

[MarioH]

Yes, iceweasel is firefox under debian.

[MarioH]

By the way, when I deactivate javascript, the entry page looks like this:

[yellowled]

Yes, iceweasel is firefox under debian.

I'm sorry, but I have no way to test an outdated Firefox with reasonable effort.

Someone (ideally Klaus) please try this in Iceweasel:

1. Go to “New entry”
2. Open the dev tools console (in German, that's Extras → Web-Entwickler → Web-Konsole in a recent Firefox; I hope that even exists in Iceweasel …)
3. Click the buttons which don't works
4. Post whatever output shows up in the console here

Thanks!

YL

[yellowled]

By the way, when I deactivate javascript, the entry page looks like this:

I think that's about how it's supposed to look with no JS …?

YL

[MarioH]

I think that's about how it's supposed to look with no JS …?

Yes, I just wanted to show because Onli asked if he has javascript enabled. If not, he won't see any buttons and the tags field would just be there.

Mario

[yellowled]

Yes, I just wanted to show because Onli asked if he has javascript enabled. If not, he won't see any buttons and the tags field would just be there.

Oh, okay. Sorry, I'm getting hypersensitive to anything that could be a bug report already.

YL

[u1amo01]

Ahem. Brought back my "real" blog to the old version and created a brand new blog with 2.0 Beta 2. And every thing is fine. Hmmm.

I could try to copy my old blog, make the update again and have a look what happens.

Could be difficult to find the reason for this strange thing.

[yellowled]

And every thing is fine. Hmmm.

Yeah, I'm pretty sure this is not a bug in s9y or Iceweasel.

YL

[u1amo01]

It's not a browser problem.

I have the following event plugins installed:
[serendipity_event_spartacus]
[serendipity_event_spamblock]
[serendipity_event_typesetbuttons]
[serendipity_event_autosave]
[serendipity_event_textile]
[serendipity_event_staticpage]
[serendipity_event_smartymarkup]
[serendipity_event_freetag]

I moved them all to "Inactive" and the problems are gone.

Then I put them back to "Active", one after the other (in the order displayed above). The trouble started again after activation of serendipity_event_autosave. I have activated all of the plugins again without autosave and everything is fine.

I deleted serendipity_event_autosave Vers. 0.2.2 in the backend, installed it again - and the same problem is here again.

[yellowled]

I deleted serendipity_event_autosave Vers. 0.2.2 in the backend, installed it again - and the same problem is here again.

So apparently, it's an issue with serendipity_event_autosave. That's an untested plugin from additional_plugins (which is one of the reasons why the 2.0-beta should not be tested in production yet).

Thanks for testing that further!

YL

[garvinhicking]

Yeah sadly the autosave plugin is so complex I never gotten the hang of it...we're really in need of a dev who could check on that. Or maybe we could approach it differently and actually create an autosave-functionality within the core backend, using some jquery plugins?!? Speaking of that, I faintly remember someone (onli?) already created some proof of concept for it? Hhm...