[eluser]Thoer[/eluser]
I know the answer, I have debugged it earlier.
You have a field name called "body" or "content" in your database.
You need to find it in the "clean_blue" view files and change the ids for the elements having these names. I changed mines to "codex-body" and "codex-content". Then you change "assets\clean_blue\css\codex_clean_blue.css" correspondingly. (It should be line 160,164, 168.)
It should be fixed.
[eluser]Thoer[/eluser]
Can't promise, because I have appointments and deadlines for pretty much every day this week, but I'll try to take a look.
[eluser]abmcr[/eluser]
Thank you,
[eluser]cu3edweb[/eluser]
[quote author="Thoer" date="1213707794"]I know the answer, I have debugged it earlier.
You have a field name called "body" or "content" in your database.
You need to find it in the "clean_blue" view files and change the ids for the elements having these names. I changed mines to "codex-body" and "codex-content". Then you change "assets\clean_blue\css\codex_clean_blue.css" correspondingly. (It should be line 160,164, 168.)
It should be fixed.[/quote]
Thanks a lot that took care of the problem. Will this be change in newer version? So we don't have to.
Thanks abmcr for the plugin.
[eluser]ocergyNohtna[/eluser]
i'm using an older version of CE that i've been modifying for some time now. i can't believe i didn't notice this before, but apparently the search function doesn't handle the pagination. when you perform a search and then click on any of the pagination links it loses the search and just shows the next set without the search affecting it. does that make sense? can anyone tell me how i'd go about persisting the search for the pagination links? should i store it in a session/cookie in order to handle such a task or is there a smarter (and possibly easier) way to handle this?