Search found 15 matches

by DLange
Mon Apr 27, 2020 4:41 pm
Forum: Development
Topic: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?
Replies: 9
Views: 2082

Re: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?

This has not been added (backported) to 2.3.5 so it is still broken out there.
@thh, could get the commits from master (57cbaaa and d690a75) lined up for the next maintenance release?
(And @mentions don't work in phpBB :-))
by DLange
Wed Mar 25, 2020 11:26 pm
Forum: Development
Topic: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?
Replies: 9
Views: 2082

Re: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?

Thanks for the quick review, the merge and the mop up on the version number bump.
by DLange
Wed Mar 25, 2020 12:39 pm
Forum: Development
Topic: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?
Replies: 9
Views: 2082

Re: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?

The problem is, as soon as you mention ONLY_FULL_GROUP_BY, this becomes MySQL / MariaDB specific. It would work down to ancient versions but I don't know what Postgres et. al. think of such SET statements. Not that anybody should run s9y with anything but MariaDB, but ... :-). Also s9y doesn't use m...
by DLange
Wed Mar 25, 2020 10:40 am
Forum: Development
Topic: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?
Replies: 9
Views: 2082

Re: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?

Actually https://riptutorial.com/mysql/example/26731/any-value-- warns against ANY_VALUE for apparently good reasons.
This did not survive a test on my blog for longer than an hour until it threw some empty values. For no apparent reason.
So ... seems the ugly solution is the way to go.
by DLange
Wed Mar 25, 2020 8:26 am
Forum: Development
Topic: Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?
Replies: 9
Views: 2082

Preferences for working around MySQL 5.6 -> 5.7 incompatibilities?

The event_spamblock plugin silently stops updating the .htaccess file once a user upgrades from MySQL 5.6 to 5.7 because the latter now defaults to a "strict" mode that will make $q = "SELECT ip FROM {$serendipity['dbPrefix']}spamblock_htaccess WHERE timestamp > " . (time() - 86400*2) . " GROUP BY i...
by DLange
Mon Feb 17, 2014 10:15 am
Forum: Bugs
Topic: Markdown "lib" option breaks footnotes
Replies: 1
Views: 1415

Markdown "lib" option breaks footnotes

v1.21 of the markdown plugin introduces the new "lib" option. Using that footnotes are not rendered (and linked) properly anymore. They show up as [^1] in the text instead of a superscript 1. There is also no link to the footnote anymore. Using the (non-default) "classic" option, footnotes work agai...
by DLange
Sun Apr 28, 2013 12:17 pm
Forum: Bugs
Topic: [Spam protector] too long lines created in .htaccess file
Replies: 9
Views: 5530

Re: [Spam protector] too long lines created in .htaccess fil

With the appended line, it works quite nicely again. In my case the 177 entries are good for about one day of spammer activity as it currently is. @Timbalu: Your code did not work for me (blog doesn't load anymore after editing the file, could be suhosin killing it, did not debug further) @Garv: I r...
by DLange
Fri Apr 26, 2013 12:09 pm
Forum: Bugs
Topic: [Spam protector] too long lines created in .htaccess file
Replies: 9
Views: 5530

Re: [Spam protector] too long lines created in .htaccess fil

I added

Code: Select all

ORDER BY timestamp DESC LIMIT 177
to the original line as a quick fix.
I'm waiting for a proper solution from Garv. Can't be that we can easily have people running that plugin DoS'd by spamming them from a few hundred IPs within two days...
by DLange
Wed Apr 24, 2013 9:18 am
Forum: Bugs
Topic: [Spam protector] too long lines created in .htaccess file
Replies: 9
Views: 5530

Re: [Spam protector] too long lines created in .htaccess fil

I like the feature and I'd keep it (otherwise I'd have to re-implement something similar via e.g. fail2ban and that's much more work).

Timbalu's proposal is a step in the right direction.
by DLange
Mon Apr 22, 2013 9:05 am
Forum: Bugs
Topic: [Spam protector] too long lines created in .htaccess file
Replies: 9
Views: 5530

[Spam protector] too long lines created in .htaccess file

The "Spam protector" plugin will write way too long lines into the .htaccess file if it has enough IPs in the database spamblock_htaccess table (within two days' time stamps). Apache will then truncate the line and interpret the remainder of an IP address as an invalid command resulting in "500 Serv...
by DLange
Fri Apr 11, 2008 12:14 pm
Forum: Bugs
Topic: serendipity_event_s9ymarkup adds </u> to URLs breaking
Replies: 5
Views: 5385

Hi @All,

my local version is fixed, thus the link mentioned in post #1 will not show the example in live action anymore.
But you can try the effect of serendipity_event_s9ymarkup breaking URLs with underscores in them out with your local serendipity blog.

Take care,
Daniel
by DLange
Fri Apr 11, 2008 12:06 pm
Forum: Bugs
Topic: serendipity_event_s9ymarkup adds </u> to URLs breaking
Replies: 5
Views: 5385

That's about priorities. I always prefer not breaking stuff over functionality, but it's obviously your choice to make. I can always patch my local copy (which I'll do, as it breaks my article).
by DLange
Fri Apr 11, 2008 10:43 am
Forum: Bugs
Topic: serendipity_event_s9ymarkup adds </u> to URLs breaking
Replies: 5
Views: 5385

Hi Garvin,

how about making the regex require (whitespace followed by understore) for <u> and (underscore followed by whitespace) for </u>? There are no whitespaces in URLs and this will not add any complexity.

All the best,
Daniel

(missing blank added in edit)
by DLange
Fri Apr 11, 2008 1:33 am
Forum: Bugs
Topic: serendipity_event_s9ymarkup adds </u> to URLs breaking
Replies: 5
Views: 5385

serendipity_event_s9ymarkup adds </u> to URLs breaking

plugins/serendipity_event_s9ymarkup/serendipity_event_s9ymarkup.php: $text = preg_replace('/\b_([\S ]+?)_\b/','<u>\1</u>',$text); does not honor URLs that may not be <u>'ified as the URL http://en.wikipedia.org/wiki/Statler_%26_Waldorf that will end up http://en.wikipedia.org/wiki/St...