I've recently cloned a website to a different domain. The template is Hivemind. Everything is the same for the moment as was hoped except that we now get the following message when we go to any page from any menu.(Interestingly, we do not get the message when we go to the Home page via clicking on the logo.) I have looked around for a solution without success. Both websites are now running on the latest joomla - 1.5.17
I noticed via google that quite a lot of websites using this template have the same problem. The message does not appear if we use a different template. Any help would be very much appreciated.
PS. Depending on what menu item we click on, the number of lines varies between 2 and 4.
Cheers from Australia
Message:
Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/youbeau1/public_html/templates/rt_hivemind/rt_styleloader.php on line 33
Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/youbeau1/public_html/templates/rt_hivemind/rt_styleloader.php on line 33
Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/youbeau1/public_html/templates/rt_hivemind/rt_styleloader.php on line 33
Thanks JEM. I got the service provider to move it - siteground - and they always seem to get things right. However, it is interesting that you mention the PHP. I've just looked and found that the original working version is running on 5.2.9 and the problem clone is on 5.1.6. Do you think this might be the clue?
The post I saw with similar errors mentioned moving from php4 to php5 (didn't mention specific versions - but in any case could be part of the issue).
After Siteground moved the site you are still experiencing the error?
I wonder what method they used...
That is, if the original files are corrupt, or a file is missing, even if they restore the site from what ever files you give them, they will wind up with the same results as you.
That's why we recommend using Akeeba....
It will create a .jpa (Akeeba native file format) or Zip file along with a copy of your DB.
The recommended method is to upload the .jpa file and run 'kickstart', (part of the Akeeba system - this will automatically extract the .jpa and start the install process) or upload the Zip file and extract it on your server and run the install (as opposed to extracting the Zip and uploading all the files via FTP).
In either case, backing up a working site, transferring the whole package, then extracting it on the server 99.9% of the time eliminates any issues with missing or corrupt files.
JEM! Good news. I changed the PHP via the cpanel and now everything seems fine. I have a lot to learn about doing backend stuff. Retired book publisher so I know that side of things but every so often I run into probs.