![Smile :)](./images/smilies/icon_smile.gif)
About those collapsible fields, we have them in general section, we have them more and more in Plugin configs and we have them in template configs. I don't think that they would allow ignoring more than a page scroll.
Sometimes it is a full stripe, sometimes a half one.
Surely just because the current one worked without major brokage and I was too afraid to update something that could prevent it. Never run a changing system.(*) Garvin, is there a reason why Xinha Core was never updated to 0.96.1 ?
I don't understand....Czorneboh wrote:Ian, the problem was not resolved with static pages version 3.99. in autumn 2012. We had not the communication about that. From how many other users you have got an "ok now"? Don knew the problem from me; we had chatted about that and reported it on 27th oct. 2012.
It still exists. So I have to use "no templates", because the one entry box is blocked. But to switch on and off the function "hide/show side bars" for static pages I have to use "simple templates". This is the only reason for me to switch to "simple templates" sometimes.
I have quite many static pages in use. The breadcrumb navigation from Don is nice to have (was on my wish list).
You mean the white emty block?Czorneboh wrote:Example for a white stripe on a static page in the frontend:Sometimes it is a full stripe, sometimes a half one.
Garvin. Is that an answer to my first question? What has an fckeditor instance have to do with it?garvinhicking wrote:In the PHP scope, we could try to detect an active fckeditor wysiwyg instance, and only if its missing we could enable that fix. I wouldn't object to that.
Hi DonDon Chambers wrote:In my humble opinion, static page navigation ... umm... sucks! Maybe we can get some collective ideas on how to improve it. [...]