problems with WA_Globals.php

Using PowerCMS - I have found using every combination known to man the WA_Globals.php - doesn't connect. Your PDF "Customizing the PowerCMS Globals file does not seem to update to the new release of 1.0.2. as the first step to define the absolute/root URL - $WAGLOBAL_Root_URL = "http://billytaylorproperties.com/" ;
<br />
however when the file was originally downloaded and in the forum on posted by neilo, March 28th at 12:40am - the files should be:<br />
<?php
$WAGLOBAL_Site_Name = "Your Site Store Name" ;

$WAGLOBAL_localRoot = "/WA_CMS/"; //relative path to your PowerCMS files on your local testing server.
$WAGLOBAL_remoteRoot = "/CMS/"; //relative path to your PowerCMS files on your remote server.

// Admin Settings
$WAGLOBAL_Admin_UserName = "yourAdminName" ;
$WAGLOBAL_Admin_Password = "yourAdminPassword" ;
?>

<br />
Myself and another computer literate collegue have tried every combination known to man to get this section to connect and after reading the forums section we are not the only ones to have trouble. Five hours trying to figure out one thing is stupid.

After several hours of going down the road of setting up a testing server according to your directions for getting started on this document it says, oh you don't need that. Great Scott!
<br />
I have tried my hostings full FTP path for the remote server and every combination of it /www.billytaylorproperties.com/web/content/CMS/

and the local server as "/" as I would like to just run remotely
<br />

I have a working knowledge of Webassist products, PHP, MySQL. I started with the new 1.0.2 never having uploaded any other extensions before so there was nothing to override.

I am trying to test my file at admin/

I have a live demo in front of my client Wednesday the 31st at 9am. I hope after supporting WebAssist since 1998 you will be able to help me figure out the problem before then.

my login is caryn@grueneacreswebdesign.com

I know phone calls are not a part of your support but one 5 second phone call could probably fix this and I can move on.

thank you,
caryn maus
830-899-2901

The WA_Globals.php file for the PowerCMS version 102 is this (as it comes in a fresh download):

<?php
  $WAGLOBAL_Site_Name = "Admin Site Title" ;
	
  $WAGLOBAL_localRoot  = "/PowerCMS folder/"; //relative path to your PowerCMS files on your local testing server.
  $WAGLOBAL_remoteRoot = "/PowerCMS folder/"; //relative path to your PowerCMS files on your remote server.  
 
  // Admin Settings
  $WAGLOBAL_Admin_UserName = "Please enter your admin username" ;
  $WAGLOBAL_Admin_Password = "Please enter your admin password" ;
?>

So as your CMS files and folders have been put in a folder on your remote server called 'CMS', the WA_Globals.php file you will upload to your remote site will be:

<?php
  $WAGLOBAL_Site_Name = "Admin Site Title" ;
	
  $WAGLOBAL_localRoot  = "/CMS/"; //relative path to your PowerCMS files on your local testing server.
  $WAGLOBAL_remoteRoot = "/CMS/"; //relative path to your PowerCMS files on your remote server.  
 
  // Admin Settings
  $WAGLOBAL_Admin_UserName = "youradminusername" ;
  $WAGLOBAL_Admin_Password = "youradminpassword" ;
?>

Don't forget to enter your own Admin username and Password.

Your CMS folder is correct, because if you go to your admin help page, you can see the correct path in the browser address bar.

If you replace 'help.php' with 'index.php' I see a blank page which indicates that there is a problem with that page. I should see a login page.

If I go directly to: users_login.php , then I see the login page.

First thing I would try would be to add error reporting code:

<?php
error_reporting(E_ALL);
ini_set('display_errors','on');
?>

to the very beginning of your CMS/admin/index.php page and re-upload it, and hopefully this should print out to the page what error is preventing the page from loading. This may help us to diagnose your problem.

My second suggestion would be to just re-upload afresh PowerCMS files and folders to the CMS directory on your remote site, having altered the WA_Globals php file as above.

The pdf you refer to is outdated and should have been replaced, and yes - that does add to the confusion.

caryn, I have been informed by Jon that you are still having trouble with this. I would like to help you out. When I visit the admin section I get a blank white page, this indicates that there is a php error occurring on the page. Please try adding in this code to the admin index page so that the error can be known:

<?php

error_reporting(E_ALL);

ini_set('display_errors','on');

?>

Once the error is known we can work to resolve it, if the problem is not one that you understand or can easily fix I would like to open a ticket for you so I can help you get this worked out. Please post back and let us know the result, I will be looking for your response.

Eric,
Here is what I got with the error code. Since I talked to Jon - I deleted the index.php and reloaded from a new download and its still broken.

Thank you,
Caryn

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /mnt/Target01/332078/352401/www.billytaylorproperties.com/web/content/CMS/admin/index.php:5) in /mnt/Target01/332078/352401/www.billytaylorproperties.com/web/content/CMS/WA_SecurityAssist/Helper_PHP.php on line 5

Warning: Cannot modify header information - headers already sent by (output started at /mnt/Target01/332078/352401/www.billytaylorproperties.com/web/content/CMS/admin/index.php:5) in /mnt/Target01/332078/352401/www.billytaylorproperties.com/web/content/CMS/WA_SecurityAssist/Helper_PHP.php on line 67

I have opened a ticket for you on this issue so that we can look into the problems further. To update the ticket please login and visit your support history.

supporthistory.php

I see. I'm assuming that my magic cloak of invisibility is finally working. The alternatives would be too depressing. Gratias tibi ago.

We got this worked out in a ticket. There were a couple of problems occurring. The first problem was that the php error reporting code was returning an error itself. This was due to a white space character outside of the php block.

This exposed the next issue which was another white space character outside of the php block but it was in the globals file.

The final issue was getting the database loaded properly. This was resolved by using the included .sql file in the database folder with phpMyAdmin to import the file. The instructions for this are included in step 1 of the read me.