CMS Made Simple Forums

Posted: **Wed May 15, 2013 10:09 pm**

Hi everyone, I'm an experienced web master, but a relatively new CMSMS user.

My client had an out-of-date installation and I upgraded them from 1.9.4 to 1.11.6. I followed the recommended path of incremental upgrades through 1.10.2 -> 1.11.2 - 1.11.5 - 1.11.6. The server is Linux, Apache 2.2.24, with MySQL 5.1.68-cll.

I also had the server admins upgrade the PHP version to 5.3.23 because we wanted to install some modules that required it (a protected content area for registered customers - but not paid access and no ecommerce).

So far so good.

Now I've installed the necessary modules, but they're not working and I don't understand why.

I've installed:

CustomContent 1.9
FrontEndUsers 1.21.15
SelfRegistration 1.7.8

I followed the instructions for FrontEndUsers and the module appears fine, with all settings set appropriately, but when I insert the tag {FrontEndUsers} it breaks the page.

The source code of the broken page does not include the <head> section of the template and instead begins with the </__body> tag.

And the source code is truncated at the point where the {FrontEndUsers} would appear, so there's no code beyond that point.

So, instead of:

Code: Select all

<__html>
<head>
</head>
</__body>
blah, blah, blah
{FrontEndUsers}
<__body>
</__html>

I've got:

Code: Select all

</__body>
blah, blah, blah

I've looked over the documentation for FrontEndUsers and haven't been able to find anything that might explain this.

And it's not just this module. The same thing happens if I try to include the SelfRegistration tag {cms_module module=SelfRegistration group=registered}. The page breaks at the point where the tag should be and the <head> section is missing.

Can anyone shed light on this?

Thanks in advance,
Jade

Posted: **Thu May 16, 2013 2:36 am**

Error logs are good for this, also check your system info page for any yellow ! or red X, it would help to paste system info here...

Posted: **Thu May 16, 2013 6:16 am**

check your template and stylesheet.

a) Open the template of the theme;
b) Search for {stylesheet};
c) Replace {stylesheet} with {cms_stylesheet};
d) Save template;
e) Open style sheets and change image calls:
old url(uploads/folder/image.jpg)
new url([[root_url]]/uploads/folder/image.jpg

Posted: **Thu May 16, 2013 3:59 pm**

Dr.CSS wrote:Error logs are good for this, also check your system info page for any yellow ! or red X, it would help to paste system info here...

There's nothing in the error logs at all. The only caution is for E_DEPRECATED being enabled.

I've removed identifying information.

CMS Install Information
CMS Version 1.11.6

Installed Modules
CMSMailer 5.2.1
FileManager 1.4.3
MenuManager 1.8.5
ModuleManager 1.5.5
News 2.12.12
nuSOAP 1.0.2
Printing 1.1.2
Search 1.7.8
ThemeManager 1.1.8
TinyMCE 2.9.12
FormBuilder 0.7.3
FormBrowser 0.4.2
CGSimpleSmarty 1.6.2
CGExtensions 1.34
Comments 1.9.2
Showtime 3.3
Gallery 1.6.1
SiteMapMadeSimple 1.2.7
GoogleMaps 0.2.1
CMSPrinting 1.0.4
MicroTiny 1.2.5
FrontEndUsers 1.21.15
SelfRegistration 1.7.8
Captcha 0.4.6
CustomContent 1.9

CMS Config Settings
php_memory_limit
process_whole_template
output_compression false
max_upload_size 50000000
url_rewriting mod_rewrite
page_extension .html
query_var page
image_manipulation_prog GD
auto_alias_content true
locale
default_encoding utf-8
admin_encoding utf-8
set_names true
debug true
root_url http://www.REMOVED.com
ssl_url https://www.REMOVED.com
root_path /home/REMOVED/public_html (0750)
previews_path /home/REMOVED/public_html/tmp/cache (0755)
uploads_path /home/REMOVED/public_html/uploads (0755)
uploads_url http://www.REMOVED.com/uploads
image_uploads_path /home/REMOVED/public_html/uploads/images (0755)
image_uploads_url http://www.REMOVED.com/uploads/images
ssl_uploads_url /uploads
use_smarty_php_tags false

PHP Information
Current PHP Version (phpversion) 5.3.23
md5 function (md5_function) On (True)
GD version (gd_version) 2
tempnam function (tempnam_function) On (True)
Magic quotes in runtime (magic_quotes_runtime) Off (False)
Is E_STRICT disabled in error_reporting (E_STRICT)
Is E_DEPRECATED disabled in error_reporting (E_DEPRECATED) E_DEPRECATED is enabled
PHP Effective Memory Limit (memory_limit) 50M
Maximum Execution Time (max_execution_time) 120
PHP output_buffering (output_buffering) On
PHP Safe Mode (safe_mode) Off (False)
File uploads (file_uploads) On (True)
Maximum Post Size (post_max_size) 50M
Maximum Upload Size (upload_max_filesize) 50M
Session Save Path (session_save_path) /tmp (1777)
Sessions are allowed to use Cookies (session_use_cookies) On (True)
Basic XML (expat) support (xml_function) On (True)
Checking for the XMLReader class (xmlreader_class) On (True)
Checking if the httpd process can create a file inside of a directory it created (create_dir_and_file)
PHP register_globals (register_globals) Off (False)
disable_functions in PHP (disable_functions)
PHP Open Basedir (open_basedir)
Test for remote URL (test_remote_url)
fsockopen: Connection ok!
fopen: Connection ok!
Test ini_set (check_ini_set) On (True)
Test for the curl library (curl) On
Test curl version (curlversion) version 7.24.0, minimum recommended version is 7.19.7

Server Information
Server API (server_api) cgi-fcgi
Server Database (server_db_type) mysql (mysql)
Server Database Version (server_db_version) 5.1.68
Check database access levels (server_db_grants) found a "grant all" statement that appears to be suitable
Server Software (server_software) apache/2.2.24 (unix) mod_ssl/2.2.24 openssl/1.0.0-fips mod_bwlimited/1.4
Server Operating System (server_os) linux 2.6.32-279.11.1.el6.x86_64 on x86_64

Permission Information
tmp /home/REMOVED/public_html/tmp (0755)
templates_c /home/REMOVED/public_html/tmp/templates_c (0755)
modules /home/REMOVED/public_html/modules (0755)
File Creation Mask (umask) /home/REMOVED/public_html/tmp/cache (0755)
config_file 0444

Posted: **Thu May 16, 2013 4:08 pm**

staartmees wrote:check your template and stylesheet.

a) Open the template of the theme;
b) Search for {stylesheet};
c) Replace {stylesheet} with {cms_stylesheet};
d) Save template;
e) Open style sheets and change image calls:
old url(uploads/folder/image.jpg)
new url([[root_url]]/uploads/folder/image.jpg

Thanks Staartmees, but that's not the issue.

I checked the template and css files and they use the correct items.

As I mentioned, it's not a matter of the <head> section being incomplete... it's simply not there.

See my example code in my original post.

The first tag in the source code is an opening </__body> tag.

The last item in the source code is the content immediately preceding either the {FrontEndUser} or {SelfRegistration}

So, from what I can tell, the existence of either of those tags is causing the head section of the template to be skipped and the remainder of the page to skipped.

Posted: **Fri May 17, 2013 2:52 am**

jadeb wrote:So, from what I can tell, the existence of either of those tags is causing the head section of the template to be skipped and the remainder of the page to skipped.

Knowing Under the Hood - How CMSMS Processes Page Templates helps to understand what's happening...

CMS Made Simple processes page templates by blocks:
outside BODY and HEAD tags; Between BODY tags; Between HEAD tags;

That means that the HEAD tag is the last to be processed (which is quite handy in most cmsms situations).
So the page brakes on the smarty tag calling the module/s. Maybe a peek at the admin Log may shed some light on this?

Posted: **Fri May 17, 2013 3:01 pm**

Jo Morg wrote:CMS Made Simple processes page templates by blocks:
outside BODY and HEAD tags; Between BODY tags; Between HEAD tags;
That means that the HEAD tag is the last to be processed (which is quite handy in most cmsms situations).
So the page brakes on the smarty tag calling the module/s. Maybe a peek at the admin Log may shed some light on this?

Wow, thanks Jo Morg. That certainly does help to understand the reason for the missing HTML HEAD sections.

But, the admin log doesn't show anything other than admin actions. And there are still no errors showing up in the server logs.

So, I'm still not sure what to try next.

Posted: **Fri May 17, 2013 6:14 pm**

At this point we may need to see your template, paste here please...

Posted: **Fri May 17, 2013 7:03 pm**

The CMSMS Admin log != http error log.

If CMSMS is dying, then something, somewhere is generating an error. You need to find it to get a hint as to what is wrong.

Posted: **Sat May 18, 2013 5:18 pm**

Dr.CSS wrote:At this point we may need to see your template, paste here please...

Thanks for the suggestion.

We've got a custom template which is quite long. But I've also tried the page with this much shorter template which also fails exactly the same way.

So, I don't think it's the template, but here goes.

Code: Select all

{process_pagedata}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<__html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>{sitename} - {title}</title>
<link href='http://fonts.googleapis.com/css?family=Arvo' rel='stylesheet' type='text/css'>
{cms_stylesheet}
{metadata}
{cms_selflink dir="start" rellink=1}
{cms_selflink dir="prev" rellink=1}
{cms_selflink dir="next" rellink=1}
</head>
</__body>
<div id="wrapper">
	<div id="header-wrapper">
		<div id="header">
			<div id="logo">
				<h1><a href="{root_url}">{sitename}</a></h1>
				<p>your slogan here</p>
			</div>
		</div>
	</div>
	<!-- end #header -->
	<div id="menu">
		{menu template="Mobility // minimal_menu" number_of_levels="1"}
	</div>
	<!-- end #menu -->
	<div id="page">
		<div id="page-bgtop">
			<div id="page-bgbtm">
				<div id="content">
					<div class="post">
						<h2 class="title">{title}</h2>
						
						<div class="entry">
							{content}
						</div>
					</div>
					<div style="clear: both;">&nbsp;</div>
				</div>
				
				<div id="sidebar">
					<ul>
						<li>
							<h2>About Us</h2>
							<p>Mauris vitae nisl nec metus placerat perdiet est. Phasellus dapibus semper consectetuer hendrerit.</p>
						</li>
						<li>
							<h2>Navigation</h2>
							{menu template="Mobility // minimal_menu" start_level="1" collapse="1"}
						</li>
						<li>
							<h2>Blogroll</h2>
							<ul>
								<li><a href="#">Aliquam libero</a></li>
								<li><a href="#">Consectetuer adipiscing elit</a></li>
								<li><a href="#">Metus aliquam pellentesque</a></li>
								<li><a href="#">Suspendisse iaculis mauris</a></li>
								<li><a href="#">Urnanet non molestie semper</a></li>
								<li><a href="#">Proin gravida orci porttitor</a></li>
							</ul>
						</li>
					</ul>
				</div>
				<!-- end #sidebar -->
				<div style="clear: both;">&nbsp;</div>
			</div>
		</div>
	</div>
	<!-- end #page -->
</div>
<div id="footer">
	<p>Copyright (c)  {current_date format="%Y"} {sitename}. All rights reserved. Original Design by <a href="http://www.freecsstemplates.org/">CSS Templates</a>.</p>
</div>
<__body>
</__html>

Posted: **Sat May 18, 2013 5:26 pm**

calguy1000 wrote:The CMSMS Admin log != http error log.

If CMSMS is dying, then something, somewhere is generating an error. You need to find it to get a hint as to what is wrong.

Thanks calguy.

I realize that the CMSMS admin log is different than the http error log.

I must not have been clear with my response regarding logs, so here goes again.

The http error log is empty.

The CMSMS admin log only contains administrators' actions and automated tasks.

So, there's nothing useful that I can see in either of those.

Perhaps there's a feature I could enable that will show more errors in the CMSMS admin log, but I'm not familiar with it and haven't seen such a setting. If so, I'd gladly turn it on to get some clues.

Thanks again.

Posted: **Sat May 18, 2013 6:55 pm**

This may help...

http://docs.cmsmadesimple.org/troubleshooting/tips

Posted: **Sat May 18, 2013 7:59 pm**

Dr.CSS wrote:This may help...

http://docs.cmsmadesimple.org/troubleshooting/tips

Thanks again, Dr. CSS.

I'd already tried that. But I tried it again.

Enabling debugging didn't produce any results on the page where I included the {FrontEndUsers} tag, presumably because the page fails at the point of the tag's insertion.

I'm pretty stumped at this point.

It's not a problem with parsing smarty tags, because there are other tags in other pages.

It's just these two plugins.

Posted: **Sat May 18, 2013 9:05 pm**

If the template you pasted is not the exact template you use then we won't be able to help you, it doesn't matter how long it is we still need to see it...

Posted: **Mon May 20, 2013 8:44 pm**

jadeb wrote:My client had an out-of-date installation and I upgraded them from 1.9.4 to 1.11.6.

I have read the whole thread and seen you have loads of modules. You might well of done the upgrade exactly right, but if they are a new client to you, you don't know what happened to their installation up until you took it over. I bet your issues are due to a dodgy file somewhere; and finding the cause might be more trouble than it's worth.

If it were me I would be considering installing a fresh version of 1.11.6, adding FEU and SelfReg and the other modules you're going to use and importing content (of course, this depends on how much content there is in the existing site). You might well find that doing it this way gets you a working website quicker in the long run?

CMS Made Simple Forums

FrontEndUsers & SelfRegistration tags - break my page

FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page

Re: FrontEndUsers & SelfRegistration tags - break my page