Hm..., bad news, my try did not help, sorry! I have to set this elsewhere.
So I will update the plugin again to 5.7.1 and will set it back to 4.5.7.1, available online tomorrow.
The rest is like I said already in my last post. (Next will then be 4.5.7.2 or even 4.5.8.0)
Search found 4580 matches
- Sun Mar 13, 2016 11:37 am
- Forum: Plugins
- Topic: new WYSIWYG-Editor event Plugin: CKEDITOR!
- Replies: 169
- Views: 156692
- Sat Mar 12, 2016 5:19 pm
- Forum: Plugins
- Topic: new WYSIWYG-Editor event Plugin: CKEDITOR!
- Replies: 169
- Views: 156692
Re: new WYSIWYG-Editor event Plugin: CKEDITOR!
Tomorrow on Spartacus! Please do not forget to upgrade your Plugin as soon as possible! This version tries to internally set back the plugin version from 5.7.0 to 4.5.7.0 in the database, to follow CKEditors versioning, which gets relevant with upcoming next major versions. Since this internal "...
- Wed Mar 09, 2016 7:30 pm
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
A larger version of this image via lightbox might be nice. Yes, that is the normal usage for lightbox'ing. And even more some galleries... But putting "/mysite/uploads/image1.jpg" into an EP field would need a case why this is necessary. At this point, I have no clue where this approach i...
- Wed Mar 09, 2016 7:10 pm
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
Ok please give me some example code to play around.
Then I can see if I get the idea to build that in....
If it is a simple path only ... why should it lightbox...?
Then I can see if I get the idea to build that in....
If it is a simple path only ... why should it lightbox...?
- Wed Mar 09, 2016 5:55 pm
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
"Ah.." :idea: - now I see... :wink: Extended properties could be problematic though, since not known. Its a users decision what kind of extended propery field is used, isn't it? [...] You mean, read at plugin config workflow all available ep fields and make them configurable by dynamic opt...
- Wed Mar 09, 2016 8:50 am
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
I asked this, since the plugin already checks these 4 markup elements: body, extended body, comments and nuggets. If you allow the default body to be checked, I don't really see a need to separate body and extended, while this is actually one entry! This is done by runtime. If delivered by single en...
- Tue Mar 08, 2016 6:14 pm
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
Did you check this isn't working already included/merged to/with the body field?
- Tue Mar 08, 2016 6:09 pm
- Forum: General discussions
- Topic: Maximum length of posts
- Replies: 5
- Views: 6579
Re: Maximum length of posts
Yes, right! Thanks for mentioning!
Again, this only may be a need, if you come up from a very old Serendipity install and the upgrades did not already touch it.
Again, this only may be a need, if you come up from a very old Serendipity install and the upgrades did not already touch it.
- Tue Mar 08, 2016 9:55 am
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
Yeah, thanks. Now netmirror has synced and the package_event_XX.xml is up to date.
- Wed Mar 02, 2016 10:22 am
- Forum: Generelles in Deutsch
- Topic: Serendipity Upgrade von 1.6.2 auf 2.0.3
- Replies: 6
- Views: 4174
Re: Serendipity Upgrade von 1.6.2 auf 2.0.3
Wenn du schon einen lokalen Webserver betreibst, wirst du dir ja sicherlich nicht jedes Zeug installieren, sondern nur Dinge denen du so weit vertraust, dass du sie dir auf deinen Rechner holst. NoScript gegen localhost laufen zu lassen ist in diesem Sinne ziemlich widersinig. Deshalb einfach die lo...
- Tue Mar 01, 2016 10:08 am
- Forum: Generelles in Deutsch
- Topic: Serendipity Upgrade von 1.6.2 auf 2.0.3
- Replies: 6
- Views: 4174
Re: Serendipity Upgrade von 1.6.2 auf 2.0.3
Wahrscheinlich ist dein serendipityPath nicht mehr derselbe.
Bis du dir sicher, dass du die Ersetzung komplett im selben Pfad vorgenommen hast?
Sonst in der "PREFIX"_config Datenbanktabelle danach suchen.
Bis du dir sicher, dass du die Ersetzung komplett im selben Pfad vorgenommen hast?
Sonst in der "PREFIX"_config Datenbanktabelle danach suchen.
- Tue Mar 01, 2016 9:28 am
- Forum: Themes
- Topic: Request: Theme config item type ="colorpicker"??
- Replies: 17
- Views: 11900
Re: Request: Theme config item type ="colorpicker"??
Must this really be in core? Isn't this possible as part of the theme only...?
- Mon Feb 29, 2016 2:09 pm
- Forum: Themes
- Topic: Request: Theme config item type ="colorpicker"??
- Replies: 17
- Views: 11900
Re: Request: Theme config item type ="colorpicker"??
HUH... Who said thisyellowled wrote:... implemented (especially as part of the core) ...
IMHO a release zip delivered theme is not part of the core. It is just pre delivered because of license and easyness.
- Sun Feb 28, 2016 10:35 am
- Forum: Themes
- Topic: user stylesheets and colorset stylesheets
- Replies: 34
- Views: 21003
Re: user stylesheets and colorset stylesheets
In set
and get.
Code: Select all
$serendipity['template_loaded_config'][$serendipity['template']] = $template_loaded_config; // copy into global scope...
Code: Select all
$colorset_file = dirname(__FILE__) . '/' . $serendipity['template_loaded_config'][$serendipity['template']]['colorset'] . '_style.css';
- Sat Feb 27, 2016 8:37 pm
- Forum: Plugins
- Topic: Lightbox bug 2.4.0
- Replies: 29
- Views: 18197
Re: Lightbox bug 2.4.0
Changing the mirror and sync paths is a total valid approach, though! They all are more than equal, and GitHub may be even more.