allwebnow
Feb 25 2008, 06:39 AM
Many times when I log into my whm area to the rvsitebuilder area, I get these similar messages. I don't know how to get rid of them permanantly. I mean i do exactly what they tell me to do and they go away for a while but they always seem to come back after either cpanel upgrade or rvsitebuilder upgrades. This is about the 3rd or 4th times I've seen these similar warning messages after I've successfully fixed them in the past. I really don't know why they keep popping up unless a cpanel upgrade resets the php.ini file to a default or something. If that's the case, can someone help me find a solution to help me get rid of these messages for good?
WARNING !!
WARNING: RVSiteBuilder recommend PHP maximum execution time of each script , in 180 seconds or above.
HELP: Edit /usr/local/cpanel/3rdparty/etc/php.ini and change "max_execution_time=180" or above, and restart cPanel service (/usr/local/cpanel/startup).
WARNING: RVSiteBuilder recommend maximum size of POST data 105M or above.
HELP: Edit /usr/local/cpanel/3rdparty/etc/php.ini and change "post_max_size=105M" or above, and restart cPanel service (/usr/local/cpanel/startup).
WARNING: RVSiteBuilder recommend maximum allowed size for uploaded files that PHP will accept 100M or above.
HELP: Edit /usr/local/cpanel/3rdparty/etc/php.ini and change "upload_max_filesize=100M" or above, and restart cPanel service (/usr/local/cpanel/startup).
pairote
Feb 25 2008, 01:28 PM
I do not see the case where cPanel reset /usr/local/cpanel/3rdparty/etc/php.ini. After make change as suggested, do you check if there is no warning in RVSiteBuilder?
azannam
Feb 28 2008, 03:33 AM
Hi
I have the same issu
3 times since last friday I had to modify php.ini
WHM 11.15.0 cPanel 11.18.1-S20683
rvsitebuilder 2.42
Peoplespaces
Mar 1 2008, 01:00 AM
QUOTE(azannam @ Feb 27 2008, 03:33 PM)

Hi
I have the same issu
3 times since last friday I had to modify php.ini
WHM 11.15.0 cPanel 11.18.1-S20683
rvsitebuilder 2.42
Same issue for me as well. I make the changes and then need to do it agin a few days later.
jljr222
Mar 8 2008, 09:47 PM
Any fix for this yet, it is becoming very annoying to edit the php.ini on the cPanel side EVERYTIME I upgrade cPanel. My techs have told me that this is because the script was not coded properly otherwise this problem would not occur. When can we expect a fix? This is the 5th time.
dotcomUNDERGROUND
Mar 9 2008, 08:54 PM
Same here.
allwebnow
Mar 10 2008, 10:20 AM
I've gone into my php.ini files about 5 times to fix this. The message goes away but just keeps coming back after every rvsitebuilder or cpanel update (don't know which one). Regardless, I've just given up on trying to update php.ini everytime as it is useless to do so until there is a real fix for this.
BTW, I'm running cpanel's release updates.
WHM 11.15.0 cPanel 11.18.2-R21613
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0
Rvsitebuilder version : PRO 2.42
pairote
Mar 10 2008, 12:10 PM
It seems cPanel reset php.ini every upcp.
We have created script to update php.ini to accomodate this. It will be available next update (v2.43). You will just need to run the following command.
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl
If you want to automate it, add above command at /scripts/postupcp (don't forget to set its permission to 700) all will be settled.
allwebnow
Mar 18 2008, 04:06 AM
Are you saying add the above command to the /scripts/postupcp? would that mean we'd paste it like this?
#!/bin/sh
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl
pairote
Mar 18 2008, 03:51 PM
Yes.
PS: I edited your post to avoid others confuse with your mscheck cript.
allwebnow
Mar 18 2008, 07:14 PM
k no prob.
dotcomUNDERGROUND
Mar 23 2008, 04:46 PM
I dont find /scripts/postupcp on my system.
Should i create one?
And on the newly created file i paste the following:
CODE
#!/bin/sh
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl
Save the file and chmod it to 777
Right?
pairote
Mar 24 2008, 11:20 AM
QUOTE
I dont find /scripts/postupcp on my system.
Should i create one?
Yes.
QUOTE
Save the file and chmod it to 777
Right?
755 should be sufficient.
Aric
Mar 31 2008, 04:39 AM
Note that just running this command via SSH as root (as suggested in the WHM RVSITEBUILDER area) doesn't work because it checks the wrong php.ini file. It decides the php.ini file is in /root/php.ini. For cPanel systems, the backend php.ini file is always at /usr/local/cpanel/3rdparty/etc/php.ini. Manually editing the script to indicate the correct php.ini file makes it work just fine.
One other very minor note... The note that is displayed if no changes are made is currently: "Nothing change. Your PHP configuration for cPanel(3rdparty) pass the minimum recommendation for RVSiteBuilder." It should be "Nothing changed. Your PHP configuration for cPanel (3rdparty) passes the minimum recommendation for RVSiteBuilder."
Regards,
Aric
pairote
Mar 31 2008, 10:42 AM
Both issues have been fixed. And will be distributed on the next update.
Randy
May 31 2008, 11:46 AM
Since I had so many problems with this issue I put in a cPanel ticket and they added these settings where they were editable in WHM -=> Tweak Settings under the PHP Section
chaloupe
Jun 4 2008, 11:05 AM
I have run the script: perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl
restart cPanel services and we still have the yellow warning.
We have also change settings in the WHM > Tweak Settings under the PHP section, restarted cpanel and stil got this yellow warning. Any fix?
QUOTE
WARNING: RVSiteBuilder recommend PHP maximum execution time of each script , in 180 seconds or above.
WARNING: RVSiteBuilder recommend maximum size of POST data 105M or above.
WARNING: RVSiteBuilder recommend maximum allowed size for uploaded files that PHP will accept 100M or above.
To avoid the problem, please SSH to the server as root and run
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl
and restart cPanel service (/usr/local/cpanel/startup).
pairote
Jun 4 2008, 11:50 AM
There is a bit changing on the latest cPanel. PHP maximum execution time, maximum size of POST data, maximum allowed size for uploaded files need to set in WHM/Tweak. We are updating autofixphpini to accomodate it. If you don't want to wait for the update, simple go to your WHM and set the value there.
catwalk
Jun 27 2008, 01:27 AM
Just wondering, will the generous upload sizes and POST data and execution times as suggested not create security problems for a server?
Are these changes compulsory and will the site builder not function properly if these changes are not allowed?
pairote
Jun 27 2008, 09:46 AM
QUOTE
Just wondering, will the generous upload sizes and POST data and execution times as suggested not create security problems for a server?
I don't see any security implication. User need to know username and password. If someone tries to do something wrong, they can easily FTP to the server other than upload something on RVSiteBuilder or cPanel File Manager.
QUOTE
Are these changes compulsory and will the site builder not function properly if these changes are not allowed?
It is not required but recommended. If you don't set those values, you may get unnecessary support requests from your end-user such as cannot upload large files, cannot publish website especially projects which contain more than 30 pages, and etc.
noname1984
Mar 28 2009, 08:15 AM
Hi,
Just some sharing info, when I updated to 3.45, it has the warning message which says something like php version with web server is not correct, so I ssh into server and run
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl then
/usr/local/cpanel/startup , but the message still occur, after that I try to put the line
perl /var/cpanel/rvglobalsoft/rvsitebuilder/panelmenus/cpanel/scripts/autofixphpini.pl into file
/scripts/postupcp, it works and no more annoying warning message.
Hope my info can help those are having the same problem with me.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.