Page 1 of 2
Problems with FrontEndUsers and CMS 0.11.2
Posted: Sat Dec 31, 2005 12:33 am
by peram
Hi.
Can anyone confirm that FrontEndUsers 0.1.5 is PHP5-"clean" ? I'm having problems with "Users&Groups->FrontEndUser management". I get the menu, but nothing happens when I click on the "buttons" (and yes - Modify FrontEndUsers Properties is checked for the group that the currently logged in user belongs to
Tia,
peram
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Sat Dec 31, 2005 8:45 am
by peram
replying to myself here just for reference. After adding php-4.4.1 and commenting out the refrence to php5 in httpd.conf, I now have what I assume is a working installation. In other words, don't use this module with php-5 yet.
Happy new year by the way !
regs,
peram
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Mon Jan 02, 2006 9:11 pm
by calguy1000
Holidays are now over, so I'll resume my php5.11 testing of all of my modules soon. VMware is the best thing since sliced bread.
I committed to svn some php5 changes before the holidays, is anybody brave enough to try these out?
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Fri Jan 06, 2006 10:50 pm
by peram
Hi.
Environment details :
OS : Linux
webserver : apache 2.0.55
cms : 0.11.2
PHP : 4.4.1
Browser : Firefox 1.5
I've just upgraded to FrontEndUsers 0.1.6 and am finding the following in /var/log/apache/error_log :
[Fri Jan 06 21:28:58 2006] [notice] SIGHUP received. Attempting to restart
[Fri Jan 06 21:28:58 2006] [notice] Digest: generating secret for digest authentication ...
[Fri Jan 06 21:28:58 2006] [notice] Digest: done
[Fri Jan 06 21:28:59 2006] [notice] Apache/2.0.55 (Unix) DAV/2 PHP/4.4.1 configured -- resuming normal operations
[Fri Jan 06 21:29:09 2006] [error] [client 192.168.10.116] PHP Notice: Undefined index: error in /srv/www/htdocs/cms/modules/FrontEndUsers/FrontEndUsers.module.php on line 682, referer:
http://nc6220/index.php?page=Medlemsliste
[Fri Jan 06 21:29:09 2006] [error] [client 192.168.10.116] PHP Notice: Undefined index: input_username in /srv/www/htdocs/cms/modules/FrontEndUsers/FrontEndUsers.module.php on line 688, referer:
http://nc6220/index.php?page=Medlemsliste
[Fri Jan 06 21:29:09 2006] [error] [client 192.168.10.116] PHP Notice: Undefined index: input_password in /srv/www/htdocs/cms/modules/FrontEndUsers/FrontEndUsers.module.php on line 692, referer:
http://nc6220/index.php?page=Medlemsliste
This is the result of pointing the browser to the page setup with FrontPageUsers and logging in. when looking at the generated html I can see that input_username, input_passwd and btn_login is all prefixed with m3 in the form. I am able to log in but still - Is this correct ?
Another thing - after logging in i'm redirected to the page I've set up, but the following is displayed :
Welcome pamunthe
Sign out
Change My Settings
This content is only available to logged in testers and and admins
This content is available to everybody else
Note the reference to customContent. This is redered as HTML and is visible in the html-page. Any pointers on what I'm doing wrong ?
regs,
Per arne
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Sat Jan 07, 2006 12:33 am
by calguy1000
I looked at this code, and I'll fix it, but shouldn't cause you any problems in the operation. they're just warnings saying that I should have done things in a more clean way.
wrt your second issue, is the {cms_module module=CustomContent} tag somewhere above your customcontent code or in your template, that would cause that issue.
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 4:57 pm
by peram
calguy1000 wrote:
wrt your second issue, is the {cms_module module=CustomContent} tag somewhere above your customcontent code or in your template, that would cause that issue.
I might be clueless and plaint stupid here but please hear me out. I've been fiddeling with this for some time now, and I aren't any closer to solve this. Just a quick recap of what I'm done :
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 5:01 pm
by calguy1000
I fixed the stuff that was causing your php notice messages, but they were only notices, and caused no real harm.
Your customcontent issues is probably because you don't have the {cms_module module=CustomContent} tag in your page.
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 6:45 pm
by peram
calguy1000 wrote:
I fixed the stuff that was causing your php notice messages, but they were only notices, and caused no real harm.
Your customcontent issues is probably because you don't have the {cms_module module=CustomContent} tag in your page.
Thanks for the quick response/resolution on that even if it wasn't the reason for my troubles. My customcontent issues are driving me mad ! To make sure that this wasn't caused by my upgrade from 0.10.x i've just reinstalled cms-0.11.2 with a fresh database. I downloaded the needed modules (UserID-0.3.5,CMSMailer-1.73.8, CustomContent-1.4.0,FrontEndUsers-0.1.6) and installed them. I then added a blank page under tags, and inserted the following :
Code: Select all
{cms_module module=FrontEndUsers}
<!--customContent: startif group=testers,admins -->
<H1>This content is only available to logged in testers and and admins</H1>
<!--customContent: else -->
<H1>This content is available to everybody else</H1>
<!--customContent: endif -->
<!--customContent: startif group=users -->
<H1>This content is only available to logged in users </H1>
<!--customContent: endif -->
then the page is redered as the attached image. I'm having this feeling that I'm doing something utterly stupid, but I can't see what I'm doing wrong. So please explain this to me as if I was a 10-year old OK
tia,
Per Arne
[attachment deleted by admin]
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 6:49 pm
by calguy1000
Change your code to this, and try again (one new line)
Code: Select all
{cms_module module=FrontEndUsers}
{cms_module module=CustomContent} <!-- this is the new line -->
<!--customContent: startif group=testers,admins -->
<H1>This content is only available to logged in testers and and admins</H1>
<!--customContent: else -->
<H1>This content is available to everybody else</H1>
<!--customContent: endif -->
<!--customContent: startif group=users -->
<H1>This content is only available to logged in users </H1>
<!--customContent: endif -->
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 7:04 pm
by peram
Still no go. I've attached 2 screenshots - 1 before logging in where you see the customContent still beeing rendered as html, and the second of me editing the page.
I guess it is something with my setup. what versions of apache, php and mysql are you running ?
regs,
Per Arne
[attachment deleted by admin]
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 7:31 pm
by calguy1000
I copied and pasted your customcontent stuff into my page, and it worked fine.
Can you post a screen capture of your modules page?
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Tue Jan 10, 2006 7:48 pm
by peram
Here it is.
[attachment deleted by admin]
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Sun Jan 15, 2006 8:19 pm
by Maria
Hi All,
I just started doing CMS last night and did a lot of quicky readings. I'm under pressure at work and I need this site up by this week.
So far everything is working , then I tried installing this FrontEndUser, but how can I put the login
part on my home page (content) ? I couldn't find documentation for this expecially for beginners like me. Please help. This might sound stupid but im really totally lost. please direct me to the right place that can help me make the login page work and also to restrict user to view only certain page on my site.
Thanks,
Maria
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Sun Jan 15, 2006 9:46 pm
by calguy1000
this tag should put the login prompts up on your content
{cms_module module=FrontEndUsers}
Re: Problems with FrontEndUsers and CMS 0.11.2
Posted: Wed Jan 18, 2006 4:43 pm
by Ryan
Okay - this has probably already been solved through some pm or topic I missed! But........ the problem you're having with CustomContent is due to WHERE you're placing the tag.
Instead of placing the in the CONTENT box - rather place it in the template area (insert it directly into the source).
Does this make sense?