Page 1 of 1

[solved] Issue with Form Builder Behaviors and Emails

Posted: Fri Mar 05, 2010 11:13 pm
by dcleckley
I am running CMSMS v.1.6.6.  Along with that, I'm running Form Builder v.0.6.1 w/ CMSMailer v.1.73.14.  

I am running into two separate issues that I think are certainly linked.  

1. I am not receiving emails from Form Builder.  CMSMailer works fine.  I've received test emails.  But when I send an email from a form, I receive no emails.  

2.  Along with not receiving emails, my Form Builder behaviors do not work at all.  I receive no change to a submission template when I fill out a form.  If I switch the behavior to redirect to a page, nothing happens.  

The site functions well otherwise.

Note: Recently, I had to change the root url in the Config.php.  This was because I developed several sites under a different domain name (folder exists under www.mysite.com/folder name).  I redirected the new domain name to the folder (not a forward) via domain manager.  This change in the config.php, or the lack thereof, could be the issue.  Here my system information and config.php:

Code: Select all

CMS Version
1.6.6

Installed Modules
CMSMailer
1.73.14
FileManager
1.0.1
MenuManager
1.6.2
ModuleManager
1.3.1
News
2.10.3
nuSOAP
1.0.1
Printing
1.0.4
Search
1.6.1
ThemeManager
1.1.1
TinyMCE
2.5.5
CGExtensions
1.17.8
CGSimpleSmarty
1.4.3
SimpleSlider
0.3
FormBuilder
0.6.1
CGGoogleMaps
1.4.1

Config Information
php_memory_limit:
 
process_whole_template:
false
max_upload_size:
8000000
default_upload_permission:
664
assume_mod_rewrite:
false
page_extension:
 
internal_pretty_urls:
false
use_hierarchy:
true
debug:
false
output_compression:
false
root_url:
[url]http://wild.sbdcgannon.org[/url]
root_path:
/home/content/d/c/l/dcleckley/html/wild	(0755)	
previews_path:
/home/content/d/c/l/dcleckley/html/wild/tmp/cache	(0755)	
uploads_path:
/home/content/d/c/l/dcleckley/html/wild/uploads	(0755)	
uploads_url:
http://wild.sbdcgannon.org/uploads
image_uploads_path:
/home/content/d/c/l/dcleckley/html/wild/uploads/images	(0755)	
image_uploads_url:
http://wild.sbdcgannon.org/uploads/images
use_smarty_php_tags:
false
locale:
 
default_encoding:
utf-8
admin_encoding:
utf-8
PHP Information:
Current PHP Version (phpversion):
 5.2.5	 
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)	
PHP Effective Memory Limit (memory_limit):
 32M	 
Maximum Execution Time (max_execution_time):
 60	 
PHP Safe Mode (safe_mode):
 Off	(False)	
Session Save Path (session_save_path):
 /tmp	(1777)	
Session Use Cookies (session.use_cookies):
 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)	
PHP output_buffering (output_buffering):
 1	 
disable_functions in PHP (disable_functions):
 	 
PHP Open Basedir (open_basedir):
 	 
Test for remote URL (test_remote_url):
	
fsockopen: Connection ok!  
fopen: Connection ok! 
File uploads (file_uploads):
 On	(True)	
Maximum Post Size (post_max_size):
 10M	 
Maximum Upload Size (upload_max_filesize):
 10M	 
Basic XML (expat) support (xml_function):
 On	(True)	
Test file_get_contents (file_get_contents):
 On	(True)	
Test ini_set (check_ini_set):
 On	(True)	
Server Information:
Server API (server_api):
cgi-fcgi	 
Server Database (server_db_type):
MySQL (mysql)	 
Server Database Version (server_db_version):
5.0.67.d7	 
Server Software (server_software):
Apache	 
Server Operating System (server_os):
Linux 2.4.21-63.ELsmp On i686	 

Permission Information
tmp:
/home/content/d/c/l/dcleckley/html/wild/tmp	(0755)	
templates_c:
/home/content/d/c/l/dcleckley/html/wild/tmp/templates_c	(0755)	
modules:
/home/content/d/c/l/dcleckley/html/wild/modules	(0755)	
File Creation Mask (umask):
/home/content/d/c/l/dcleckley/html/wild/tmp/cache	(0755)	
config_file:
0644	 	
config.php writable. It is more safe if you change permission to read-only
>>>Config.php<<<<

Code: Select all

#This is your database connection information.  Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'xxxxx.db.2099995.hostedresource.com';
$config['db_username'] = 'xxxxxx';
$config['db_password'] = 'xxxxxxx';
$config['db_name'] = 'xxxxx';
#Change this param only if you know what you are doing
$config["db_port"] = '';


#If app needs to coexist with other tables in the same db,
#put a prefix here.  e.g. "cms_"
$config['db_prefix'] = 'cms_';

#Use persistent connections?  They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;

#Use ADODB Lite?  This should be true in almost all cases.  Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;

#-------------
#Path Settings
#-------------

#Document root as seen from the webserver.  No slash at the end
#If page is requested with https use https as root url
#e.g. http://blah.com
$config['root_url'] = 'http://wild.sbdcgannon.org';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/home/content/d/c/l/dcleckley/html/wild';

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/home/content/d/c/l/dcleckley/html/wild/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/home/content/d/c/l/dcleckley/html/wild/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';


#---------------
#Upload Settings
#---------------

#Maxium upload size (in bytes)?
$config['max_upload_size'] = 8000000;

#Permissions for uploaded files.  This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';

#------------------
#Usability Settings
#------------------

#Allow smarty {php} tags?  These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;

#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;

#------------
#URL Settings
#------------

#What type of URL rewriting should we be using for pretty URLs?  Valid options are:
#'none', 'internal', and 'mod_rewrite'.  'internal' will not work with IIS some CGI
#configurations. 'mod_rewrite' requires proper apache configuration, a valid
#.htaccess file and most likely {metadata} in your page templates.  For more
#information, see:
#http://wiki.cmsmadesimple.org/index.php/FAQ/Installation/Pretty_URLs#Pretty_URL.27s
$config['url_rewriting'] = 'none';

#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';

#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy?  (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = true;

#If using none of the above options, what should we be using for the query string
#variable?  (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';

#--------------
#Image Settings
#--------------

#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php/User_Handbook/Admin_Panel/Content/Image_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';

#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/home/content/d/c/l/dcleckley/html/wild/uploads/images';
$config['image_uploads_url'] = $config['root_url'] . '/uploads/images'; 


#------------------------
#Locale/Encoding Settings
#------------------------

#Locale to use for various default date handling functions, etc.  Leaving
#this blank will use the server's default.  This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';

#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8.  If you'd like this to be different, change
#both.  Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding.  This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = 'utf-8';
$config['admin_encoding'] = 'utf-8';

#This is a mysql specific option that is generally defaulted to true.  Only
#disable this for backwards compatibility or the use of non utf-8 databases.
$config['set_names'] = true;

# URL of the Admin Panel section of the User Handbook
# Set none if you want hide the link from Error
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php/User_Handbook/Admin_Panel';

?>

Re: Issue with Form Builder Behaviors and Emails

Posted: Fri Mar 05, 2010 11:20 pm
by dcleckley
Here is some extra information that I stumbled across but forgot to add to the initial post. 

When I create a submission template, I receive the following.  This is not typical for a Form Builder install.

Thanks! Your submissions have been received.{if $fld_14 != "" && $fld_14 != "[unspecified]" }Your Name: {$fld_14}
{/if}
{if $fld_15 != "" && $fld_15 != "[unspecified]" }Your Email Address: {$fld_15}
{/if}
{if $fld_37 != "" && $fld_37 != "[unspecified]" }Which of the following best describes your job title?: {$fld_37}
{/if}
{if $fld_17 != "" && $fld_17 != "[unspecified]" }Subject: {$fld_17}
{/if}
{if $message != "" && $message != "[unspecified]" }Message: {$message}
{/if}
{if $fld_19 != "" && $fld_19 != "[unspecified]" }Send To: {$fld_19}
{/if}


In previous installs, I have never received anything like {if $fld_15 != "" && $fld_15 != "[unspecified]" }. 
I understand what the field number represent, but they've never been present in such a way before, especially with [unspecified] in the code.  Thought I might bring it up.

Re: Issue with Form Builder Behaviors and Emails

Posted: Sat Mar 06, 2010 8:08 pm
by dcleckley
Still, I have been unable to find the source of the problem here.  The config.php looks ok, but hard to say.  I just can't understand why the rest of the site works, except for this module.

This is an issue at all of my sites:

wild.sbdcgannon.org
www.thebaybreezelounge.com
www.isaacbaker.com

Re: Issue with Form Builder Behaviors and Emails

Posted: Sat Mar 06, 2010 9:27 pm
by dcleckley
I uninstalled and removed formbuilder.  Then I reinstalled the module so I'd have a fresh install and the latest version.  This did not correct the issue.

Any thoughts?

Re: Issue with Form Builder Behaviors and Emails

Posted: Sun Mar 07, 2010 1:11 am
by mayde
Unfortunately, I'm unable to offer advice, but just wanted to comment and say that I'm having the exact same problem. Everything seems to be set up properly and I'm able to send a test email from CMSMailer. I'll be watching this thread for any solutions to this problem.

Re: Issue with Form Builder Behaviors and Emails

Posted: Sun Mar 07, 2010 9:19 pm
by dcleckley
mayde wrote: Unfortunately, I'm unable to offer advice, but just wanted to comment and say that I'm having the exact same problem. Everything seems to be set up properly and I'm able to send a test email from CMSMailer. I'll be watching this thread for any solutions to this problem.
So, you have the behavior issue as well?  Also, can you tell me more about your install?  What version are you running right now? I am going to upgrade to 1.6.7 to see if this alleviates the problem, but I highly doubt so.  I say that because I have the most updated version of Formbuilder and the core is operating fine.  Please post your system information as I have, including any other pertinent info so that others can fully assess the situation. 

One more question: Did you do a direct install to a host, or did you make a subfolder under your main host?

Re: Issue with Form Builder Behaviors and Emails

Posted: Mon Mar 08, 2010 3:35 pm
by mayde
I'm running version 1.6.7 of CMS Made Simple, version 0.6.1 of Form Builder, and version 1.73.14 of CMSMailer, as well as PHP 5 on my web host (Blue Host). I did a direct install to the public_html directory.

I'm also unable to receive any emails from Form Builder, even though the test emails I send from CMSMailer work fine.

When I submit the form, I'm brought back to the form submission page, with all the fields blank. I don't see the submission template, and I'm not redirected to another page when I choose that option instead.

The form I'm using is based off the default Contact form that comes with the install, but I added a few text input fields and a textarea. The *Email Results to set Address(es) field is set to send the emails to my Yahoo account (for testing purposes).

I haven't changed any of the CMS Made Simple files on the server since the initial install; once it was set up, I've been working exclusively in the web interface.

To see the form I'm talking about, you can visit: http://artvest.com/contact.html
(Disregard the rest of the site design. It's still under construction.)

Apart from this module, I've had no trouble setting up the rest of the site, and all of my other modules (CMSMailer, FileManager, FormBuilder, MenuManager, ModuleManager, News, NFS, nuSOAP, PageBlocks, Printing, Search, ThemeManager and TinyMCE) seem to be working properly.

Unfortunately, I haven't had much time to work on this issue over the weekend, but hope to play around with it some more tonight. I've put many hours into this new website and need to have it finished soon, so I'm eager to find a solution to this problem.

Re: Issue with Form Builder Behaviors and Emails

Posted: Mon Mar 08, 2010 4:33 pm
by dcleckley
mayde wrote: I'm running version 1.6.7 of CMS Made Simple, version 0.6.1 of Form Builder, and version 1.73.14 of CMSMailer, as well as PHP 5 on my web host (Blue Host). I did a direct install to the public_html directory.

I'm also unable to receive any emails from Form Builder, even though the test emails I send from CMSMailer work fine.

When I submit the form, I'm brought back to the form submission page, with all the fields blank. I don't see the submission template, and I'm not redirected to another page when I choose that option instead.

The form I'm using is based off the default Contact form that comes with the install, but I added a few text input fields and a textarea. The *Email Results to set Address(es) field is set to send the emails to my Yahoo account (for testing purposes).

I haven't changed any of the CMS Made Simple files on the server since the initial install; once it was set up, I've been working exclusively in the web interface.

To see the form I'm talking about, you can visit: http://artvest.com/contact.html
(Disregard the rest of the site design. It's still under construction.)

Apart from this module, I've had no trouble setting up the rest of the site, and all of my other modules (CMSMailer, FileManager, FormBuilder, MenuManager, ModuleManager, News, NFS, nuSOAP, PageBlocks, Printing, Search, ThemeManager and TinyMCE) seem to be working properly.

Unfortunately, I haven't had much time to work on this issue over the weekend, but hope to play around with it some more tonight. I've put many hours into this new website and need to have it finished soon, so I'm eager to find a solution to this problem.
This is the exact issue that I am having.  I appreciate your details as well.  There were some that you placed in your post that I didn't have.  Its good to see that we are running different versions as well.  This kills the notion that the cmsms versions might be at issue.  I didn't believe so anyway because the core is good.

Re: Issue with Form Builder Behaviors and Emails

Posted: Mon Mar 08, 2010 7:29 pm
by mayde
Figured it out (with the help of the IRC chat, of course)! Turns out, the page I had the form on did not have a regular {content} block. Instead, I was using three different blocks in my page template, all written as {content block="..."}. Each template needs to have at least one regular {content} block in order for the FormBuilder module (and other modules) to function correctly. Let me know if you need further explanation.

Hope this helps.

Re: Issue with Form Builder Behaviors and Emails

Posted: Thu Mar 11, 2010 4:16 pm
by dcleckley
In the email template, or the HTML template?

Re: Issue with Form Builder Behaviors and Emails

Posted: Sat Mar 13, 2010 12:16 am
by mayde
In the HTML template.

For example, the following template wouldn't work:

Code: Select all

{global_content name='Header'}

<div id="content">

     <div class="column_left">
            {content block="LeftColumn"}
     </div>

      <div class="column_right">
            {content block="RightColumn"}
      </div>

</div> <!-- end content -->

{global_content name='Footer'}
Instead, one of the content blocks should just be called {content}, as follows:

Code: Select all

{global_content name='Header'}

<div id="content">

     <div class="column_left">
            {content}
     </div>

      <div class="column_right">
            {content block="RightColumn"}
      </div>

</div> <!-- end content -->

{global_content name='Footer'}
Let me know if that answers your question.

Re: Issue with Form Builder Behaviors and Emails

Posted: Sat Mar 13, 2010 11:42 pm
by dcleckley
mayde wrote: In the HTML template.

For example, the following template wouldn't work:

Code: Select all

{global_content name='Header'}

<div id="content">

     <div class="column_left">
            {content block="LeftColumn"}
     </div>

      <div class="column_right">
            {content block="RightColumn"}
      </div>

</div> <!-- end content -->

{global_content name='Footer'}
Instead, one of the content blocks should just be called {content}, as follows:

Code: Select all

{global_content name='Header'}

<div id="content">

     <div class="column_left">
            {content}
     </div>

      <div class="column_right">
            {content block="RightColumn"}
      </div>

</div> <!-- end content -->

{global_content name='Footer'}
Let me know if that answers your question.
This fix is confirmed.  Placing the {content} tag within the template will correct behavioral issues and you will receive emails.  This, for some reason, has changed recently.  The Form Builder did not work like this until 1.6.6.

Thank you.l

Re: [solved] Issue with Form Builder Behaviors and Emails

Posted: Fri May 07, 2010 11:06 am
by ofrost
I am running CMSMS v.1.7.1 with Form Builder v.0.6.2 | CMSMailer v.2.0

I have the same problem and {content} tag doesn't solve it. I always had one. Any ideas?  

My problem is solved. It was .htaccessfile that caused troubles.

Re: [solved] Issue with Form Builder Behaviors and Emails

Posted: Fri May 07, 2010 6:30 pm
by Dr.CSS
Just for everyone's information the need for {content} in the page template for modules has been that way for quite some time...

Don't ever make a template with out it...