I’ve edited wp-config with no luck.
My host says it doesn’t use php.ini – running php as Litespeed (apache) not cgi.
Then try contacting your hosts for assistance with increasing your memory. Or reduce the number of plugins you are using.
Actually, I’m successfully running the plugin on a test site so I doubt the problem is with the host?
Problem solved by removing code:
'fs-link' => array(
'name' => 'fs-link',
'title' => __('Slide link','frontpage-slideshow'),
'description' => __('When the user is clicking onto the picture, this URI is used. Leave blank to set this post link as the slide link (if this option is activated into <a href="options-general.php?page=frontpage-slideshow">the plugin admin page</a>)','frontpage-slideshow'),
),
Probably not the best solution – guess the problem will reappear when the plugin is updated – but at least it works for me now.
Thanks for a great plugin! Love it!
Plugin Author
jeff_
(@jeff_)
Wow wow wow… Micke123 cans you tell me how you came to the point that was that portin of code that was messing ???????
Here is absolutely no link between this portion of code and your problem…
I was getting desperate and as the problem occured after “Slide link” on create post page I thought maybe that could somehow solve it.
Why it worked I don’t know – but it did.
I realise that the actual problem is somewhere on my installation but I’ve got no idea where and as everything is now working I’m not to bothered about it.
Easiest way is to replace every instance of
<div class="postbox closed"> with
<div class="postbox"> in frontpage-slideshow.php – that simply opens all the closed boxes. I’ve had the same problem on nearly all blogs with custom themes where I’ve used the slideshow. I suspect there’s a JS conflict somewhere or other issue, but simply opening the boxes is the quick and easy fix (for me at least).
Plugin Author
jeff_
(@jeff_)
ok good to know for the next version
