Volcano
Nov 19 2006, 12:48 PM
I mentioned this awhile back...whenever a trial user creates a site and clicks the "preview" link, they get a long delay followed by a "page not found" error. This actually creates several orphaned processes on my server and I have to restart apache to get rid of them. Publishing works, but the preview has never worked for the trial users. This happens with any browser and I just updated to the latest version (1.55).
Any chance this is going to be fixed? If not, please remove the preview in the trial pages so they won't keep generating orphaned processes.
Volcano
Nov 25 2006, 09:12 PM
QUOTE(Volcano @ Nov 19 2006, 12:48 AM)

I mentioned this awhile back...whenever a trial user creates a site and clicks the "preview" link, they get a long delay followed by a "page not found" error. This actually creates several orphaned processes on my server and I have to restart apache to get rid of them. Publishing works, but the preview has never worked for the trial users. This happens with any browser and I just updated to the latest version (1.55).
Any chance this is going to be fixed? If not, please remove the preview in the trial pages so they won't keep generating orphaned processes.
Is this issue being addressed?
Volcano
Apr 26 2007, 08:16 PM
QUOTE(Volcano @ Nov 25 2006, 10:12 AM)

QUOTE(Volcano @ Nov 19 2006, 12:48 AM)

I mentioned this awhile back...whenever a trial user creates a site and clicks the "preview" link, they get a long delay followed by a "page not found" error. This actually creates several orphaned processes on my server and I have to restart apache to get rid of them. Publishing works, but the preview has never worked for the trial users. This happens with any browser and I just updated to the latest version (1.55).
Any chance this is going to be fixed? If not, please remove the preview in the trial pages so they won't keep generating orphaned processes.
Is this issue being addressed?
Still waiting to see this get fixed. Customers are running away when they try the demo and click Preview and get a "page not found" error. It makes RV SiteBuilder (and me) look bad at a critical "first impression" time for the potential customer.
pairote
Apr 27 2007, 09:56 AM
We don't find this issue on the our tryout demo. What's your tryout website version? Go to tryout website log in as admin, does any update link appear? At least give me cPanel info for this tryout so we can fix it for you.
Volcano
Apr 27 2007, 10:56 AM
QUOTE(pairote @ Apr 26 2007, 10:56 PM)

We don't find this issue on the our tryout demo. What's your tryout website version? Go to tryout website log in as admin, does any update link appear? At least give me cPanel info for this tryout so we can fix it for you.
I am running the latest version...RVSitebuilder PRO 1.70. Tryout version 1.16. What "cpanel info" do you need?
pairote
Apr 27 2007, 11:44 AM
cPanel account of the tryout website.
apiruk
Apr 28 2007, 04:04 PM
SSH to the server and take a look on the file /var/cpanel/rvglobalsoft/rvsitebuilder/var/log/php_log.txt. Does any error show in the log? If nothing in the file, please follow the debugging instruction below.
===========
How to debugging
===========
1. Go to root WHM/RVSiteBuilder Manager/system configuration. Under logging options, change 'Enable logs' to 'Yes'. And set priority to debug. If you cannot access to that page, SSH to server as root and edit file /var/cpanel/rvglobalsoft/rvsitebuilder/var/{your_server_ip}.default.conf.ini.php. Under [log], configuration to something like this.
[log]
enabled=1
type=file
name=var/log/php_log.txt
priority=PEAR_LOG_DEBUG
2. SSH to server and run tail -f /var/cpanel/rvglobalsoft/rvsitebuilder/var/log/php_log.txt.
3. Go to RVSiteBuilder and access to the page that you experience the problem. Watch the log above, you may find the error in the log.
4. After fix the issue, go to root WHM/RVSiteBuilder Manager/system configuration. Under logging options, change 'Enable logs' to 'Yes'. And set priority to emergency. Without doing this, the log files will max out 2 GB in a few months and break RVSiteBuilder. If it occurs, remove file /var/cpanel/rvglobalsoft/rvsitebuilder/var/log/php_log.txt will fix the problem.
If you cannot fix the problem using the debug information, attached me the log file or give me root access. I will fix it for you. Please email root password separately to apiruk@rvglobalsoft.com. Don't submit it to ticket system, as it will appear on the internet. In case dedicated IP address required to access your server, please add 203.156.87.99 to your allowed host list.
Example email formatting:
Body:
IP: 203.150.224.16
Root password: password
Admin usernmae (required if su needed to be root): admin
Admin password: password