by adding two slashes at the very beginning of each mentioned line …
this prevents from stopping searchin for string lower as the defined minlenght and allows the output from the drawSearchresults method

I’m using LiveSearch manager to cache my files as I keep getting an error on the search page, but it’s getting stuck at about 1682 files and never finishes. Same thing works on a site with less links perfectly. Anything I can look for that may be causing this?

the https is done in htaccess file : RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.sibureautique.com/$1 [L,R=301] – If I delete these lines and I change url to http in livesearch.class.php it’s works well

hi, the default server port of HTTPS is 443 https://en.wikipedia.org/wiki/HTTPS and cannot be set via the .htaccess – the question is – is you server able to access your website on specifc port (you could try a wget)

Hi
Is it possible to view the image search results with lightcase/lightbox instead of opening it in a separate window?
The img tag just needs to have ‘data-rel=’lightcase’’ to initiate lightbox, but I’m just not sure where to add it to your script.

there’s the array returned by $LiveSearch->search() which could be used to produce your output – and the method drawSearchresults() which you could modify (or duplicate, rename and modify) in the class directly to fit your needs

I’m trying to install your script on a client’s site but it seems to hang when I start the cacheing process from lsMngr. I can see that it creates a SearchStrings.php and a tmpContentUrls.php (so it can write to the folder okay) but these contain nothing more than the search terms and the baseurl. If I turn on the saveUrl function, it will only produce one file called 0.url. The search page consistently returns no results.

The site is hosted with Heart Internet and their database reports the following: “If your script attempts to make an HTTP connection to a URL on the same server, it will fail. This is called a loopback connection, and we block those connections because they can be exploited by attackers.”

I haven’t seen a similar problem reported on your comments page. Could this be a Heart Internet problem, or have I missed something else?

the webserver itself acts as client to browse the website – there’s no other way to access the client-side output of the website – so the webserver needs access to your website …

you could try url_fopen and curl as connection method – if both failed Heart Internet really blocked accessing their hosted websites from being called from their hosted websites.

the only quick idea I have in your case is to create the cache from another server and use the cached files in your installation and just use the search functionality, not the cache and index functionality …

webserver or website should offer the documents UTF-8 decoded i.e. by setting the header (such as header(“Content-Type: text/html; charset=utf-8” ); and you should probably disable $utf8DecodeResults because the data is alreade decoded

Just disabling $utf8DecodeResults solved the character coding issue naturally. (all pages have charset=utf-8)

Sorry to bother with different issue, but it seems the default display of the number of pages is vertically ! which usually is not desirable. I would like to display page numbers horizontally, but in livesearch.css I couldn’t find the code for li and ul used in drawPagination function. Could you please let me know where to edit the code? I assume I should add a display: inline; to some li elements, right?

One quick question please:
On my site I can see that there are searches with spam words (like xxx, porn, etc).
I assume that these are probably automatic searches.
So I would like to know if there is a way to set up a list of banned words… which will return nothing ( exit() ) or something.
Thanks.