I upgraded one of my development instances of CMS MS from 1.11.9. to 1.11.11. Then I upgraded the FEUsers module from 1.24 to 1.25, with the XML upload approach, since I was afraid that I would run into the known memory leak problem again (see here: http://forum.cmsmadesimple.org/viewtopi ... =3&t=55024). Again here I ran into the problem, that the upgrade via XML upload is not properly recognized:
The "Modules" section tells me:
FrontEndUsers 1.24 Needs Upgrade
But when I click on "About", then I can see that indeed version: 1.25.1 is installed.
But the actual problem is, that the FrontEndUsers module does not work anymore on that instance. When I click on it, I simply get redirected back to the backend "Home" page. Accordingly I am not able to edit users there.
The System Info by the way also shows the old version of the FEUsers module:
----------------------------------------------
Cms Version: 1.11.11
Installed Modules:
CMSMailer: 5.2.2
FileManager: 1.4.5
MenuManager: 1.8.6
ModuleManager: 1.5.8
News: 2.14.4
Printing: 1.1.2
Search: 1.7.11
ThemeManager: 1.1.8
TinyMCE: 2.9.12
CGExtensions: 1.44.3
FrontEndUsers: 1.24
CustomContent: 1.10
JQueryTools: 1.2.6
Uploads: 1.18.4
CGCalendar: 1.14.3
CGSimpleSmarty: 1.7.4
CompanyDirectory: 1.22.5
AireLibs: 1.3.2
CMSPrinting: 1.0.5
MicroTiny: 1.2.7
Gallery: 2.0.1
Statistics: 1.1.3
CGUserDirectory: 1.4.5
EventsManager: 1.2.7
TreeManager: 0.6.0
Forum: 0.9.4
CGSmartImage: 1.16.2
Config Information:
php_memory_limit:
process_whole_template:
max_upload_size: 128000000
url_rewriting: none
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true
Php Information:
phpversion: 5.4.4-14+deb7u12
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 2048
E_DEPRECATED: 0
memory_limit: 512M
max_execution_time: 60
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 128M
upload_max_filesize: 128M
session_save_path: /var/lib/php5 (1733)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
Server Information:
Server Api: apache2handler
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.38
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No filesystem time difference found
----------------------------------------------
[SOLVED] Why did FEUsers stop working?
- stefhoesli
- Forum Members
- Posts: 56
- Joined: Mon Sep 19, 2011 1:06 pm
- Location: Zurich, Switzerland
[SOLVED] Why did FEUsers stop working?
Last edited by stefhoesli on Mon Dec 15, 2014 9:09 am, edited 1 time in total.
Re: Why did FEUsers stop working?
There should be an "Upgrade" link to the right side where all the other modules are listed as "Installed"
Uploading a module via XML is just that... uploading. The next step is to install or upgrade....
Uploading a module via XML is just that... uploading. The next step is to install or upgrade....
"The art of life lies in a constant readjustment to our surroundings." -Okakura Kakuzo
--
LinkedIn profile
--
I only speak/write in English so I may not translate well on International posts.
--
--
LinkedIn profile
--
I only speak/write in English so I may not translate well on International posts.
--
- stefhoesli
- Forum Members
- Posts: 56
- Joined: Mon Sep 19, 2011 1:06 pm
- Location: Zurich, Switzerland
Re: Why did FEUsers stop working?
I was afraid, that this would break the CMS again... But it worked!
Thanks a lot!
Thanks a lot!