Serendipity Forums

Hi!

Please have a look at the serendipity_event_typesetbuttons-plugin, the buttons do not seem to work anymore:

I defined
Cheers

Dirk

Hi!

Thanks. This can very well be as the WYSIWYG integration has been worked over. Didn't have the time to check yet, but I also added this as a github issue so that we keep it as blocking for the RC: https://github.com/s9y/Serendipity/issues/114

Regards,
Garvin

garvinhicking wrote:Thanks. This can very well be as the WYSIWYG integration has been worked over. Didn't have the time to check yet, but I also added this as a github issue so that we keep it as blocking for the RC: https://github.com/s9y/Serendipity/issues/114

Thank you Garvin. Where do you like bug reports more? GitHub or forum?

Cheers

Dirk

Hi!

I personally try to cover things in the boards, but when I see issues that I myself cannot deal with, it's good to have them in a list/tracker. That shouldn't be your problem though - I'd copy threads from here to the issue tracker. Ideally I believe the forum receives more specific attention. What do others think?

Regards,
Garvin

garvinhicking wrote:I personally try to cover things in the boards, but when I see issues that I myself cannot deal with, it's good to have them in a list/tracker. That shouldn't be your problem though - I'd copy threads from here to the issue tracker. Ideally I believe the forum receives more specific attention. What do others think?

I think issues should be visible in both worlds and link to each other.

Cheers

Dirk

garvinhicking wrote:What do others think?

I think it's two worlds, really.

As a developer, I prefer to file bugs I spot myself directly in the GitHub issue tracker, just because it saves time. I can imagine a lot of users would be more comfortable reporting bugs in the forums, though. I'm happy to “translate” any bug reported here to GitHub.

However, anything that might require a discussion should be reported in the forums.

YL

I can take a look at this issue. I think I already found out what the problem is. I will also try to clean up this plugin a little bit.

Guys, I spend the greater part of this day coding, refactoring and unit testing - and found it to be very enjoyable! Maybe that's because I've been dealing with a lot of DevOps stuff at work and hardly wrote any PHP code lately

Anyway, I created an almost completely reworked version of the typesetbuttons plugin that should work with both versions < 2.0 and the current beta. If you want to test it, make sure to install the very latest version from GitHub! I chatted with Matthias (yellowled), and he had to make some changes to the backend editor so that everything works as expected.

If you use this plugin (Dirk, I'm looking at you), please be so kind and test if everything works ok (on a test installation, of course). If possible, test it with s9y 1.7.* or older, too. I wrote unit tests first to ensure that nothing breaks backwards compatibility, but the original code was so ... peculiar that I can't guarantee anything

I uploaded version 0.20 of serendipity_event_typesetbuttons to my Dropbox and will leave it there for a while.

Thanks,
mattsches

Hi!

Does not work for me.

I get a "<undefined></undefined>" for every self-defined button.

No information under the info item.

Cheers

Dirk

I suppose you tested against the 2.0 branch? Did you pull in the latest changes from GitHub? This commit is crucial, otherwise it won't work.

Is there any output in the Firebug console/Chrome dev tools console? This might be a JS issue ...

Matthias

mattsches wrote:I suppose you tested against the 2.0 branch? Did you pull in the latest changes from GitHub? This commit is crucial, otherwise it won't work.

I downloaded the tar.gz-file you offered.

mattsches wrote:Is there any output in the Firebug console/Chrome dev tools console? This might be a JS issue ...

I don't use any of those tools.

Now I cloned the additional_plugins-repository and it does not work either. This time no output is generated.

Cheers

Dirk

Lux wrote:I downloaded the tar.gz-file you offered.

That will only work with a recent Git checkout of the 2.0 branch of the s9y core since it relies on things included there since beta2.

Lux wrote:I don't use any of those tools.

In Chrome, it's very easy. Load page, and then I guess it's [Alt] + [Crtl] + J (I only know the shortcut on OS X, which does't have Ctrl). Whatever output is in that window (that's the Console) could be relevant. Some of it will only appear after you interact (e.g. by clicking buttons).

YL

Hi, I've installed the latest s9y-version from github, the plugin from Matthias dropox and Chromium.

With Debian Linux it's shift ctrl J

And the output of Console is
"Failed to load resource: the server responded with a status of 404 (Not Found) "

Not very helpful, I fear.

u1amo01 wrote:"Failed to load resource: the server responded with a status of 404 (Not Found) "

Not very helpful, I fear.

Not without the name of the resource it failed to load, which should be displayed at the end of that line in the console.

If it's jquery.min.map, that doesn't help much, either. (That's a technical error, which should be fixed in the browser and should not block the rest of the JS from being executed.)

YL

Failed to load resource: the server responded with a status of 404 (Not Found) http://u1amo01.de/blog/serendipity.js&v=1397649512

No idea about 1397649512. But when I look into the source of my blog, there's this number again in the head:
" <link rel="stylesheet" type="text/css" media="screen, projection" href="http://u1amo01.de/blog/serendipity.css?v=1397649512">"

In the index.tpl of my theme I have the following code: