4952 Posts in 14417 Topics by 1491 members
|Go to End|
2 January 2010 at 7:53pm
I cannot access my admin CMS page in SS.
I get this message:
[Warning] parse_ini_file() has been disabled for security reasons
Line 4 in /home/iturner/public_html/sapphire/parsers/BBCodeParser.php
Here's that Line 4:
/*Seting up the PEAR bbcode parser*/
$config = parse_ini_file('BBCodeParser.ini', true);
$options = &SSHTMLBBCodeParser::getStaticProperty('SSHTMLBBCodeParser', '_options');
$options = $config['SSHTMLBBCodeParser'];
3 January 2010 at 6:31am
Where are you installing SilverStripe ?
This message means your hosting server administrator has disabled parse_ini_file() PHP functions. If it's your server, try to find in your php.ini config file the line beginning with "disable_functions" directive like :
disable_functions = exec,passthru,shell_exec,system,proc_open,popen,curl_exec,curl_multi_exec,parse_ini_file,show_source
in this example, functions 'exec', 'passthru', etc are disable.
3 January 2010 at 5:28pm Last edited: 3 January 2010 5:29pm
4 January 2010 at 9:17am
Thanks to all in this community for good support
I emailed my server/host (host2x.com) about this problem and they told me that deleting the parsing syntax might help; I deleted it and now the CMS works again. I do not know the future repercussions doing this will have, but it works for now.
P.S.: I only experienced this problem with the HIGHERGROUND theme...
Oh, and, by the way, THE BLOG MODULES DO NOT WORK-- FOR ANY OF MY 4 SILVER STRIPE-BASED WEB SITES
Thanks again and happy new year
5 January 2010 at 2:08am Last edited: 5 January 2010 2:09am
...they told me that deleting the parsing syntax might help; I deleted it...
What have you changed in Silverstripe ?
...THE BLOG MODULES DO NOT WORK-- FOR ANY OF MY 4 SILVER STRIPE-BASED WEB SITES...
What are the problems ?
5 January 2010 at 7:27am
Thanks for the reply.
I deleted the first 5-6 lines of parsing syntax (near the top) of: public_html/sapphire/parsers/BBCodeParser.php
Like I said, I hope it does not come back to bite me. I also upgraded to 2.3.4 and have no problems anymore. Hmm...
|Go to Top|