Module Manager can not be accessed

[ohemstock]

Hi,

[version 2.1.5 "high rock"]

I can no longer access the module manager, when I click on the link to attempt to open it, I get some kind of error message - reads like this:

Notice

The versions displayed here represent the latest XML files uploaded to the CMSMS module repository. They may or may not represent the latest available versions. Additionally, the module repository may only contain modules released within the last few months

Use at Your Own Risk

The modules displayed here are contributed by both the CMSMS Developers and independent third parties. We make no guarantees that the modules available here are functional, tested, or compatible with your system. You are encouraged to read the information found in the help and about links for each module before attempting the installation.

Installed
Search
Available Modules
Settings

This notice targets the current window and appears in place of the module manager. The links at the bottom are not active and the only way to get back is to navigate back with the browser. This came on after I installed a couple of modules (SEOTools, Formbuilder, and Extended Content Blocks).

How can I fix this please?

[paulbaker]

SEOTools and SEOTools2 are not CMSMS version 2 compatible so by installing it you may have messed something up. If you can get to the site information page (see my signature) post what it says there.

[velden]

You can disable a module by renaming it's folder in the '/modules' folder.

So e.g rename /modules/SEOTools to /modules/_SEOTools

Note that did doesn't uninstall the module (database tables and entries created during installation won't be deleted).

[ohemstock]

You can disable a module by renaming it's folder in the '/modules' folder.

So e.g rename /modules/SEOTools to /modules/_SEOTools

Note that did doesn't uninstall the module (database tables and entries created during installation won't be deleted).

Hi thanks for the advice, I have done this and it has allowed me back into the module manager, however there is a new problem - it seems that the content manager now will not load and shows an error:

Debug: (0.015138) - (usage: 1027728) - (peak: 1032504) Number of elements: 4
Array
(
[content_id] => 3
[parent_id] => 2
[item_order] => 1
[content_alias] => templates-and-stylesheets
)
Error Page Hierarchy

And, this has also prevented the website from loading at all...

The problem has worsened!

[ohemstock]

SEOTools and SEOTools2 are not CMSMS version 2 compatible so by installing it you may have messed something up. If you can get to the site information page (see my signature) post what it says there.

Hi Paul,

Here it is:

Cms Version: 2.1.5
Installed Modules:
AdminSearch: 1.0.2
CMSContentManager: 1.1.1
DesignManager: 1.1.1
FileManager: 1.5.2
MicroTiny: 2.0.3
ModuleManager: 2.0.4
Navigator: 1.0.3
News: 2.50.5
SEOTools: 1.5
Search: 1.50.2
Snippet: 0.1.2

Config Information:
php_memory_limit:
max_upload_size: 128000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/London
permissive_smarty: false

Php Information:
phpversion: 5.6.25-1~dotdeb.7.1
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_ALL: 22527
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 128M
max_execution_time: 360
register_globals: Off (False)
output_buffering: 4096
disable_functions: pcntl_alarm, pcntl_fork, pcntl_waitpid, pcntl_wait, pcntl_wifexited, pcntl_wifstopped, pcntl_wifsignaled, pcntl_wexitstatus, pcntl_wtermsig, pcntl_wstopsig, pcntl_signal, pcntl_signal_dispatch, pcntl_get_last_error, pcntl_strerror, pcntl_sigprocmask, pcntl_sigwaitinfo, pcntl_sigtimedwait, pcntl_exec, pcntl_getpriority, pcntl_setpriority,
open_basedir:
test_remote_url: Success
file_uploads: On (True)
post_max_size: 128M
upload_max_filesize: 128M
session_save_path: /var/lib/php5/sessions (1733)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
check_ini_set: On (True)
curl: On

Performance Information:
allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: On (True)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: On (True)
Server Information:
Server Software: Apache
Server Api: cgi-fcgi
Server Os: Linux 3.2.68-vs2.3.2.17-ukservers On i686
Server Db Type: MySQL (mysqli)
Server Db Version: 5.6.32
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

Permission Information:
tmp: /home/users/uks85463/html/testsite.hemstockdesign.co.uk/tmp (0755)
tmp_cache: /home/users/uks85463/html/testsite.hemstockdesign.co.uk/tmp/cache (0755)
templates_c: /home/users/uks85463/html/testsite.hemstockdesign.co.uk/tmp/templates_c (0755)
modules: /home/users/uks85463/html/testsite.hemstockdesign.co.uk/modules (0755)
uploads: /home/users/uks85463/html/testsite.hemstockdesign.co.uk/uploads (0755)
File Creation Mask (umask): /home/users/uks85463/html/testsite.hemstockdesign.co.uk/tmp/cache (0755)
config_file: 0444
----------------------------------------------

[paulbaker]

This came on after I installed a couple of modules (SEOTools, Formbuilder, and Extended Content Blocks).

I wonder if your new problem is caused by Extended Content Blocks which is not v 2 compatible either:
http://dev.cmsmadesimple.org/projects/econtentblocks

I'm not sure how you get rid of that though....uninstall in module manager?

[Rolf]

Go to "System Information" and check the functions under the tab "Cache and content".

[velden]

Go to "System Information" and check the functions under the tab "Cache and content".

I presume "System Information" --> ("Site Admin" ->) "System Maintenance"

[ohemstock]

Hi All,

thanks for your advice - in the end I just solved the problem by exporting all the designs and uploads and flattening the server directory.

It's a build in progress and there was no proper content yet, so fresh install and a few hours reloading the layout and it sorted.

Sure there is a better, less extreme way to fix this!

Cheers!