Posted by akmal143 on September 7, 2012 at 12:40am
I'm facing this problem when trying to install openscholar in GoDaddy hosting "Fatal error: Call to undefined function os_include() in /home/admin/public_html/open/profiles/openscholar/openscholar.profile on line 497" Can anyone help me to solve and give idea about this. Thank you in advance :)
Comments
hope this helps
I faced similar kind of problem:
I think you should increase max_execution_time and other time entries in the php.ini.
Nitvirus is right about the
Nitvirus is right about the php.ini file. I think this error is pretty common for Openscholar until you've made the necessary allowances in php.ini.
Once in Godaddy, open up your "file manager". Go to the folder "public_html". Create a new file named php.ini . Edit the file and then paste in this line of code (without quotes, but including the semicolon)
"set_time_limit(0);"
If its the same thing that happens to me everytime I install Openscholar, the processes take too long (Openscholar is resource hungry), and you end up getting the error. The php.ini file and the line of code that I included, allow your php process to keep going without a timeout, thus enabling Openscholar to install. Let us know if it works for you!
Hi mohhess, thanks for the
Hi mohhess,
thanks for the suggestion already tried on global php.ini, still is not working.
Hi, This may also happen
Hi,
This may also happen because of permission issues. It happened to me once. The tar.gz download has all files belonging to the wheel user. I was getting undefined function errors. Once i chown'd the openscholar files to httpd, installation went on smoothly. It happened only once and on other occations i did not face this error even if the files belong to wheel. I'm not sure why. I have not used godaddy so i'm not sure how to chown in godaddy. This may be the issue, worth a try.
Hi dbinoj, Thanks for the
Hi dbinoj,
Thanks for the suggestion, actually right now we are using suphp, so i dont think changing the file ownership will solve the problem. Do you have any idea about this?
One last thought. Try
One last thought. Try uploading or making a new .htaccess file. Sometimes upon extraction, a host will add an extension to this file making it look like (.htaccess.txt) which makes it not work. I'm not sure that it would throw that error, but its always something to try.
Just another note for the future. When I've upgraded from an older version to the beta14 version, we would get fatal errors. I had to clear the tables and do reinstall everything to get rid of the error. Which version are you using?