CMS Made Simple Forums

I have a client that is also determined to stay with the worst and most expensive hosting available. I'm running CMSMS v1.67 with MySQL 4.0.24 and getting a yellow (!) caution symbol. I haven't run into any issues so though... Don't know whether I dare upgrade them to CMSMS 1.9 though.

Sorry to dig up this old thread but I just ran into this same problem. Having any php.ini file in the admin/ folder (even an empty one or one containing session.use_cookies = 1 ) causes the login screen to appear in Image Manager. Removing the php.ini from admin/ fixes it again. No need to reply. Ju...

Especially now that they work 

You are more than forgiven klenkes, you're a legend! How on earth did I miss that? Obviously my PHP skills aren't too great either! I spent all day yesterday (mostly in action.default.php) echoing variables that still showed intact (> &) symbols. I've just commented out the line you mentioned an...

During another fun-filled day with this ::) I've discovered that gt; DOES work in SQL because during an advanced search (myvar>3), SQL receives the following: SELECT * FROM cms_module_mymodule_mylevel A  WHERE A.myvar > '3' ORDER BY item_order Which works perfectly. However, this direct SQL query: {...

Of course, get some sleep It's the middle of the night for you!

Normally plger is pretty active but his profile page says he hasn't logged on since February 4. I'll keep plugging away and reply here if I solve it. Cheers.

Thanks again Kendo. I really appreciate your help. WYSIWYG is definitely turned off. I've also disabled WYSIWYG from the options tab. Under Site Admin / Global Settings, Disallow WYSIWYG editors on global content blocks: is selected I have tried putting the smarty in the template, directly after the...

I can now confirm that you are right kendo! I've just turned the debugger on (why didn't I think of that earlier ::) ) and received the following output: (mysql): SELECT * FROM cms_module_mymodule_mylevel A  WHERE A.variable > 3 ORDER BY item_order Error (1064): You have an error in your SQL syntax;...

Thanks for the fast reply kendo. You're probably right but the module's help page gives this example: {cms_module module="mymodule" what="mylevel" query="A.date_modified > '2009-03-15' AND A.active = 1"} ...so I assume the author must have tested it with > at some stage...

I have scoured the forums but can't find anyone else with this problem... Using CTLModuleMaker v1.8.9.3, direct SQL queries like this one.... {cms_module module="mymodule" what="mylevel" query="A.variable = 5"} Work perfectly, matching any item with variable=5, however ...

OK, I'm having some success here. I've managed to fix the problem by editing /modules/yourmodulename/ action.search.php  and changing this code ... if(count($itemlist) == 0 && $emptytemplate != "**"){ echo $this->ProcessTemplateFromDatabase($emptytemplate); }elseif($template == FAL...

This thread might help.

I thought I'd dredge up this old thread because I think I have a solution that I've tested with the 'long text' field type. The following option settings will result in 'no results' for a 'simple mode' search... Should this field be indexed for the Search Module? YES Should this field show up in the...

I should have included the following version numbers too:

I'm using:
CMSMS Version
1.6.7

CTLModuleMaker
1.8.9.3

I've had the same problem. FYI I've submitted a bug report here