I am new to WordPress as well as website functioning. The site I am trying to maintain is not mine, I have been asked to the webmaster. The site was professionally designed and set up on a web hosting server. The owner had it moved to a different web host. One of the many problems that has occurred in the transfer is the loss of the sphider search plugin. When attempting to re-install it I get the following error message:
Could not create directory. /hsphere/local/home/actsion/actsion.com/wp-content/plugins/sphider/
The sphider sql database is still listed in the hosting server’s MySQL database.
How do I install sphider plugin in WordPress?
Also in the transfer I lost the ability to add and maintain sliders on the home page. How do I rectify this dilemma?
]]>Is anyone working on an update to this? It looks like it no longer works with the current versions of WordPress and PHP.
]]>I get the following Error messages:
– Failed to parse address “_http” NOHOST
or
Disallowed files and directories in robots.txt:
…
1. Retrieving: https://… at 11:35:12.
Unreachable: http 403
What do I have to do?
]]>I’m using the plugin and it seems to work perfectly with WP 3.3.2
As the reindex is triggered only when there is a page update, i want to set up a cron job on our server. I have tested the commandline but it does not seem to do anything:
cd /var/www/site.com/htdocs/wp-content/plugins/sphider/admin/
/usr/bin/php spider.php -u https://site.com/page5 -r -d 2PHP seems to run the page but nothing is happening. Anyone else having this problem with the plugin version of Sphider?
]]>The plugin fails to set up it’s required database tables and so error messages appear everywhere.
]]>I’ve installed the plugin and get the following error(s) when trying to index the site:
Deprecated: Function ereg() is deprecated
Deprecated: Function eregi_replace() is deprecated
On various lines of the file sphiderfuncs.php
I’m using PHP 5.3.3. In doing a search for this error message it indicates that 5.3.x PHP no longer supports that function directly.
Has anyone else experienced this? And, what would be the fix?
]]>