CMS Made Simple Forums

using cmsms 1.11.4 and FEU 1.21. well here we go:

----------------------------------------------

Cms Version: 1.11.4

Installed Modules:

CMSMailer: 5.2.1
CMSPrinting: 1.0.3
FileManager: 1.4.3
MenuManager: 1.8.4
MicroTiny: 1.2.5
ModuleManager: 1.5.5
CGBlog: 1.9.8
Search: 1.7.7
ThemeManager: 1.1.7
SEOTools2: 1.1.1
Showtime: 3.2
CGExtensions: 1.31.2
CGSimpleSmarty: 1.5.2
CGEcommerceBase: 1.3.11
FrontEndUsers: 1.21
JQueryTools: 1.1.1
Captcha: 0.4.5
Products: 2.18.4
CustomContent: 1.8.3
Cart: 1.8.4
CGPaymentGatewayBase: 1.1
SelfRegistration: 1.7.2
PaypalGateway: 2.3.9
Orders: 1.13.3
FormBuilder: 0.7.3
CGGoogleMaps: 2.4.3
FRTaxes: 1.1.1
CGCalendar: 1.10.0.1
ContentAliases: 0.7
SubsectionHeaders: 0.1


Config Information:

php_memory_limit:
process_whole_template:
output_compression:
max_upload_size: 64000000
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


Php Information:

phpversion: 5.3.15
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 128M
max_execution_time: 90
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 64M
upload_max_filesize: 64M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)


Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.23
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable


----------------------------------------------

I can't seem to include two FEU tags in the same template or page even though they are separated by custom content if /else statement. When trying to save a template with two FEU tags the template won't save and i get a broken white page with no error in cmsms admin log or in filesystem error log and no messages if debugging is on. Same thing happens if i have one FEU tag in header and one in content section of a specific page and i visit that page. I can kind of understand it with this frontend example but it is as if the backoffice is being treated like the frontend when trying to save a template. Is this a limitation in the core's smarty implementation or FEU? or is this a bug? if bug, is it with the core or FEU?
btw, this is one of the versions of what i'm trying to add to a template thanks.

ok, upon further testing it is not the attempt at using two FEU tags, it is which FEU tags i attempt to use. {FrontEndUsers},{FrontEndUsers form="logout"},{FrontEndUsers form="changesettings"}, and {FrontEndUsers form="lostusername"}don't work whether i am logged in on the front end or not. by "don't work" i mean no css used by the page and no more html from the FEU form start and beyond, when using one of the above FEU tags/templates. If i try to apply using these tags in the template it ignores me. if i force a submit it breaks the admin page. same situation as on the front end. no errors, no css and html missing after the offending call. Any ideas appreciated.

Trying to narrow down the point of failure... Am assuming from what you said below that the form start appears in the underlying frontend html?

At what point does it break in the form? Maybe there is a Smarty var that it cannot evaluate in the form(s).

Also: check adminlog for errors and, if nothing comes up there, turn debug mode on... that may give some more clues on what that error might be.

Thanks for the responses!

@psy: I was not clear about when the break occurs in the page. The form does not start. evidently, smarty cannot parse the FEU tags i have listed above at all. The page breaks at these tags whether trying to view a front end page or submit a back office template.

@jo morg: unfortunately, debug won't display on these broken pages either and nothing turns up in admin log or in public_html/error log either. also, no errors,warnings, or notices with error reporting and display errors turned on. of course it doesn't appear to be php related so that makes sense.

I'm going to take a look at the module code and the templates for these tags, but any ideas welcome. hmmm, i seem to remember tag parameters that were not exactly right in a module's help file before. I wonder if that could be the case again.