Hi!
A 503 Error should show up in your CGI/Apache Error log to get the specific details. Maybe your server's mod_Security or something like that blocks specific input variable?
Regards,
Garvin
Search found 29949 matches
- Thu Oct 12, 2017 10:49 am
- Forum: Generelles in Deutsch
- Topic: Serendipity-Treffen 2018
- Replies: 27
- Views: 17007
Re: Serendipity-Treffen 2018
Grundsätzlich glaube ich an Werbefinanzierung und will das unterstützen, daher nein. Leider überreizen es manche Seiten...Benutzt Du keinen Werbeblocker? uBlock origin beispielsweise?
LG,
Garvin
- Mon Oct 09, 2017 3:22 pm
- Forum: Generelles in Deutsch
- Topic: Serendipity-Treffen 2018
- Replies: 27
- Views: 17007
Re: Serendipity-Treffen 2018
Hab auch teilgenommen, und heilige Bannersau, Batman - ist Doodle inzwischen eine Ansammlung an Werbefläche!
- Mon Oct 09, 2017 3:15 pm
- Forum: Bugs
- Topic: WYSIWYG-Editor insterts br tags
- Replies: 2
- Views: 3541
Re: WYSIWYG-Editor insterts br tags
Do you maybe have the nl2br event plugin installed? That one transform newlines to break tags, which you don't really need when you use WYSIWYG <p> Tags.
- Thu Sep 14, 2017 1:39 pm
- Forum: Installation
- Topic: Admin backend dropdowns suddenly inactive
- Replies: 4
- Views: 5986
Re: Admin backend dropdowns suddenly inactive
Hi,
the error message refers to a non existing variable; what it should show you is that the database table "serendipity_entryproperties" is missing. Usually that one is created with the serendipity installation; is it missing on your installation?!
the error message refers to a non existing variable; what it should show you is that the database table "serendipity_entryproperties" is missing. Usually that one is created with the serendipity installation; is it missing on your installation?!
- Thu Sep 14, 2017 1:05 pm
- Forum: Installation
- Topic: Version 2.1.1 PHP 7.0, no mysql
- Replies: 1
- Views: 3173
Re: Version 2.1.1 PHP 7.0, no mysql
There is no Mysql option available for Database Type in the Configuration setup when running the installer. Only PDO::SQLite and SQLite3 are options. Is this because of PHP 7.0? This might be because you only installed the "php7" package, and maybe not "php-mysqli" or other data...
- Thu Sep 14, 2017 12:43 pm
- Forum: Generelles in Deutsch
- Topic: WICHTIG: Umzug funktioniert nicht
- Replies: 11
- Views: 9623
Re: WICHTIG: Umzug funktioniert nicht
Hi! Wir haben einen utf8-migration Github branch, wo ich versucht habe alle Keys für utf8mb4 kompatibel zu machen: https://github.com/s9y/Serendipity/tree/feature_utf8mb4 Da am besten mal in die sql/db.sql reinschauen. Eigentlich müsste der Upgrader wenn man jene Version installiert die Datenbank mi...
- Thu Sep 14, 2017 12:37 pm
- Forum: General discussions
- Topic: Empty entries
- Replies: 2
- Views: 3571
Re: Empty entries
That sounds very odd. Do you have any event plugins that might interact with this? It shouldn't happen by default that new entries are inserted.
- Wed Aug 02, 2017 4:01 pm
- Forum: Installation
- Topic: Updated Debian to Stretch and now s9y delivers double-UTF8
- Replies: 3
- Views: 5064
Re: Updated Debian to Stretch and now s9y delivers double-UT
Hi! The easiest thing to debug what issues one has with database charsets is to start as low level as possible. Write a "utf8test.php" script: <?php $c = mysqli_connect('localhost', 'root', 'supersecretpassword'); mysqli_select_db($c, 'serendipity'); header('Content-Type: text/plain; chars...
- Wed Aug 02, 2017 1:27 pm
- Forum: Plugins
- Topic: $view not working with serendipity_event_customarchive
- Replies: 6
- Views: 9154
Re: $view not to working with serendipity_event_customarchiv
I don't remember, but you shouldn't run those older versions of serendipity anymore anywayszarzanola wrote:So no versions before 2.0 would be suitable?
- Wed Jul 26, 2017 11:42 am
- Forum: Plugins
- Topic: $view not working with serendipity_event_customarchive
- Replies: 6
- Views: 9154
Re: $view not to working with serendipity_event_customarchiv
Hi! It would work for any s9y version after 2.0 - where we upgraded to Smarty 3, which required us to change some init things around. @Christine: The additional smarty init is there for the case that the archive plugin is called on pages or embedded blogs, where the smarty object has not yet been in...
- Wed Jul 12, 2017 4:02 pm
- Forum: Plugins
- Topic: $view not working with serendipity_event_customarchive
- Replies: 6
- Views: 9154
Re: $view not to working with serendipity_event_customarchiv
Which Serendipity version are you using? Did you actually try to disable the customarchive plugin and does your template check on $view then work? Because actually inserting the "return true" in the genpage hook of the plugin file should really bypass any other assignment of the serendipit...
- Mon Jul 10, 2017 1:38 pm
- Forum: Plugins
- Topic: 'Show Entries in sidebar' plugin - random order?
- Replies: 7
- Views: 19444
Re: 'Show Entries in sidebar' plugin - random order?
Hey, for the time being you could try to edit the plugins/serendipity_plugin_showentries.php file and replace this: $entries = serendipity_fetchEntries(null, true, $limit, false, false, 'timestamp DESC', '', false, true); with: $entries = serendipity_fetchEntries(null, true, $limit, false, false, 'R...
- Mon Jul 10, 2017 1:36 pm
- Forum: General discussions
- Topic: At wits end....
- Replies: 7
- Views: 7115
Re: At wits end....
Sorry for that experience
I think it might have something to do with the old paths still residing in the .htaccess file that you might need to adapt, or the templates_c/ cache might have needed a purge.
I think it might have something to do with the old paths still residing in the .htaccess file that you might need to adapt, or the templates_c/ cache might have needed a purge.
- Wed May 17, 2017 11:00 am
- Forum: Generelles in Deutsch
- Topic: Anlegen von DB-Tabellen (durch Plugins) - Collation?
- Replies: 6
- Views: 5013
Re: Anlegen von DB-Tabellen (durch Plugins) - Collation?
Hi! Was davon würde fehlschlagen? Ginge "NOT NULL"? Oder "MEDIUMTEXT"? Oder "TIMESTAMP" und "DEFAULT CURRENT_TIMESTAMP"? Mediumtext, timestamp UND default current_timestamp :-) Anderswo im Code habe ich {UTF_8} an dieser Stelle gesehen. Wie wird denn das erset...