CMS Made Simple Forums

I upgraded from 1.9.3. where Search module page was functional. After 1.9.3. to 1.9.4. Search module page displays only word Search and nothing else so I cannot restore default template and I don't have Reindex button or anything else. I done 1.9.4. installation from scratch on other computer and there is also nothing on Search module page.
Tnx very much for your efforts.

Sorry, I done it all again on clean computer and now the ModuleManager and Search module pages are all quite excellent. So I fixed it on server, too. One of php files inside modules/Search directory turned to binary file but I cannot find why. I replaced all files in that directory with fresh files from cms 1.9.4. tar.

After that I emptied all tables cms_module_search_XXX and on Search module page engaged "Reindex all content", choosed for search and result template "Restore to Defaults" but search is still not working.

Result page is empty and nothing is written to cms_module_search_words table.

Table cms_module_search_items has 666 records and value in only row in cms_module_search_items_seq is 666.
Table cms_module_search_index has 63308 records.

I made page inside cms with {search} as only content. Tried but no luck.

I managed to fix the module manager by retracing the steps but adding new pages remains a problem. as mentioned above, new pages are added to the database but do not show in the admin - Content - Pages list. once i clear the cache under global settings all pages get listed. bizarre.

Module Manager patch worked for me (1.9.3 to 1.9.4 upgrade)
Thanks Ronny!

My Module Manager was showing on the menu, but nothing would happen when I was clicking on the menu items, and I wasn't getting any errors either!

This patch fixed it, thank you

Search is still my problem.
I upgraded from realy old version to 1.9.3, then diff to 1.9.4.
I use pretty urls and .htaccess is:

# BEGIN Optional settings

# Turns off directory browsing
# not absolutely essential, but keeps people from snooping around without
# needing empty index.html files everywhere
#Options -Indexes
#Options -Indexes
ServerSignature Off
#Options +FollowSymLinks

# Deny access to config.php
# This can be useful if php ever breaks or dies
# Use with caution, this may break other functions of CMSms that use a config.php
# file. This may also break other programs you have running under your CMSms
# install that use config.php. You may need to add another .htaccess file to those
# directories to specifically allow config.php.
<Files "config.php">
order allow,deny
deny from all
</Files>

# Sets your 403 error document
# not absolutely essential to have,
# or you may already have error pages defined elsewhere
#ErrorDocument 403 /forbidden403.shtml

# No sense advertising what we are running
ServerSignature Off
# END Optional Settings

# BEGIN CMSMS and Rewrite Rules
# Make sure you have Options FollowSymLinks
# and Allow on

RewriteEngine On

# Might be needed in a subdirectory
#RewriteBase /

#
# 301 Redirect all requests that don't contain a dot or trailing slash to
# include a trailing slash
RewriteCond %{REQUEST_URI} !/$
RewriteCond %{REQUEST_URI} !\.
RewriteRule ^(.*) %{REQUEST_URI}/ [R=301,L]
# URL Filtering helps stop some hack attempts
#IF the URI contains a "http:"
RewriteCond %{QUERY_STRING} http\: [OR]
#OR if the URI contains a "["
RewriteCond %{QUERY_STRING} \[ [OR]
#OR if the URI contains a "]"
RewriteCond %{QUERY_STRING} \] [OR]
#OR if the URI contains a "<__script__>"
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
#OR script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
#OR any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2}) [OR]
#OR if the URI contains UNION
RewriteCond %{QUERY_STRING} UNION [OR]
#OR if the URI contains a double slash
RewriteCond %{QUERY_STRING} // [OR]
#OR if the URI contains a *
RewriteCond %{QUERY_STRING} \*
#then deny the request (403)
RewriteRule ^.*$ - [F,L]
# End URL Filtering

# CMSMS Rewriting
# Set assume mod_rewrite to true in config.php and clear CMSMS cache
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
# END CMSMS

# END Rewrite rules

Annoying thing is also that I set my home page to "Pages" but when I enter admin mode I'm almost never redirected to "Pages". Language is changing by itself from Croatian to English but my account settings are Default page "Pages" and default language: "English".

Hi RonnyK, thanks - your patch solved my module manager problems. I had upgraded from 1.8.2 -> 1.9.4 and was getting an incomplete module manager page and a javascript error.

Thanks again

paulbaker wrote:Hi RonnyK, thanks - your patch solved my module manager problems.

I upgraded an old CMS 1.4.1 (!) to 1.9.4 in three steps for DB schemas'smooth upgrade, the module manager was the only little thing which didn't follow happily.

Thank you RonnyK

Installation went fine. But there is again problem with css.
Admin site works ok, but main page shows only unformatted text - neither theme works.

MySQL 5.5.9, OS: Linux 2.6.32.26+drm33.12, PHPv: 5.2.14

I'm still having trouble with search module. So I did 1.9.4. clean install on my home computer, activated pretty urls and made all adjustments to cmsms as on my production site.

Search was working fine on all pages of default install. Then I changed template for all pages to nCleanBlue, set it to default and search is only working on home page. On any other page search is not working.

Then I changed default template to CSSMenu top + 2 columns, applied it to all pages and search is working on all pages.

So I suspect that something inside nClenaBlue and similar templates is making search unusable. Any idea what???

By removing following lines from .htaccess I managed to get search working again:

RewriteCond %{REQUEST_URI} !/$
RewriteCond %{REQUEST_URI} !\.
RewriteRule ^(.*) %{REQUEST_URI}/ [R=301,L]