Search found 14 matches
- Tue Oct 19, 2010 3:36 pm
- Forum: Layout and Design (CSS & HTML)
- Topic: Menu problem with different colored / styled divs
- Replies: 1
- Views: 803
Menu problem with different colored / styled divs
I'm trying to build menu like this: <div class="menu_green"> <ul> <li><a href="#">Parent1</a> <ul> <li><a href="#">Child1</a></li> <li><a href="#">Child2</a></li> <li><a href="#">Child3</a></li> <li><a href="...
- Thu Jun 04, 2009 8:46 am
- Forum: [locked] CMSMS MLE fork
- Topic: Default_lang doesn't do anything
- Replies: 1
- Views: 1915
Default_lang doesn't do anything
Ok, in my config_lang.php I have: define('DEFAULT_LANG', 'fi_FI'); $force_mle_default = true; $hls = array( 'fi_FI' => array( 'block'=>'fi', 'flag'=>'suomeksi', 'text'=>'suomeksi', 'locale'=>'fi_FI.utf8@euro', ), 'en_US' => array( 'block'=>'en', 'flag'...
- Mon Nov 10, 2008 8:14 pm
- Forum: Modules/Add-Ons
- Topic: Problem with FrontEndUsers module
- Replies: 1
- Views: 959
Problem with FrontEndUsers module
Just installed FrontEndUsers module on CMSMS 1.4.1. I created one user group and added one user. Login seems to be fine, but after login and redirection to secured page, it shows "You are not authorized to view this data". The code fragment is here: {if $customcontent_loggedin} {content}...
- Fri Oct 31, 2008 4:49 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Ok, tried to downgrade from 1.4.1 to 1.1 to see ??? Apart security concern, apart changed DB (and maybe incompatibility), apart if you downgrade a module you have less functionalities, we not support old versions Alby Well, just to check if there are any issues concerning older db content, if I cou...
- Fri Oct 31, 2008 3:47 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Ok, tried to downgrade from 1.4.1 to 1.1 to see, if there some kind of compatibility issues with 1.4.1 and old db content. I got everything up and running and went to check the site, but the menus were empty. I went to check Layout -> Menu Manager and got this error: Call to a member function GetFri...
- Thu Oct 30, 2008 3:28 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Ok, got that. Now the problem is, if I put also child pages into items list, they are seen on same menu level as parents.alby wrote:with item to select that list of pages ONLYdapam wrote: why isn't its children seen on menu?
Alby
- Thu Oct 30, 2008 10:50 am
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Ok, the remaining problem is this. If I have in my template {menu template='uniadmmenu' collapse='1' items='home,how-to-apply'} and and I'm on the how-to-apply page, why isn't its children seen on menu? This worked fine when I used {menu template='uniadmmenu' collapse='1' includeprefix='home,how-to-...
- Wed Oct 29, 2008 7:08 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
By the way, I got it working using parameter items, strange. This still isn't nice, because I have to go through all the templates and replace the prefixes with whole aliases.
Edit: doesn't work correctly, child nodes aren't shown...
Edit: doesn't work correctly, child nodes aren't shown...
- Wed Oct 29, 2008 6:21 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
For example, if I have this row in template: {menu template='uniadmmenu' collapse='1' includeprefix='home'}, what db queries are made? Is the page / content found by query like select * from cms_content where content_alias = 'home'? That query found the "content" from db, but somehow the C...
- Tue Oct 28, 2008 5:24 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Cracked ? May I suggest " recovering from an exploit " ? I hope you have good database backups. Pierre Yep, cracked. Actually I did what you suggested in that topic. The host was cleaned throughly and only database backup could be used. Luckily the backup is good, but the problem that thi...
- Tue Oct 28, 2008 12:31 pm
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
In system verification "This function will compare the checksums found in the uploaded file..." To what uploaded file should I compare my system against? I created checksum.dat file from my system when it was installed yesterday evening, so should I compare it against that? No, in downloa...
- Tue Oct 28, 2008 11:56 am
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
- Run System Verification in Admin Panel and checking for missing/broke file - Remove lib and modules/MenuManager folders and re-uploads them Just tried, no help. Something else, that I could try. System Verification is all ok? Active debug in config.php and look for other info/errors and in your e...
- Tue Oct 28, 2008 8:47 am
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Re: Problems after updating from 1.1 to 1.4.1
Just tried, no help. Something else, that I could try.alby wrote: - Run System Verification in Admin Panel and checking for missing/broke file
- Remove lib and modules/MenuManager folders and re-uploads them
Alby
- Tue Oct 28, 2008 6:11 am
- Forum: CMSMS Core
- Topic: Problems after updating from 1.1 to 1.4.1
- Replies: 16
- Views: 3831
Problems after updating from 1.1 to 1.4.1
Hello! I'm quite newbie with CMSMS, so please bear me. I've just got a project to update CMSMS from v1.1 to v1.4.1. The main reason for this is, that the site got hacked pretty badly because of old version of CMSMS. I'm using MySQL 5.0 and I'm not sure about PHP version (installation informed that v...
