I have a very large website that I have split over five Freeway files. I wanted to add the Simple Site Search action across this site but it seems to be restricted to working with only one Freeway file.
When I applied the action to the site folder I had hoped it would ‘see’ all the items within it. However it only appears to ‘see’ the folders explicitly used within the one Freeway document I was testing it on.
Does this mean that I can’t use this suite of search actions or is there a way I could get around this problem?
My reason for wanting to use this action, and upgrading the site files to version 5.5 in preparation, is that some site pages are password protected so using a ‘normal’ Google search wouldn’t work. I had hoped to add access to the site search within the members only area and use this suite of actions to generate a full index of the site.
I have a very large website that I have split over five Freeway
files. I wanted to add the Simple Site Search action across this
site but it seems to be restricted to working with only one Freeway
file.
If you split your site into multiple documents, I don’t think that SSS
can generate a combined index. It could create a separate index for
each document’s worth of site, and if you structure your site so that
the search within each “silo” makes sense, then you could probably get
along with this. But you might need to reconsider splitting the site
if you want to use SSS for your search.
Other members of this list have made great strides with the PHP search
engine SPhider. You might want to search the list and see. That system
uses a separate indexing “crawler” that you run on the server whenever
you make an update to the site, so it can work with a mixture of
static and dynamic content, unlike SSS. The index is stored in MySQL,
and the search engine and results page are written in PHP. I fooled
with it once many years ago, and it was pretty simple then. I hear
it’s gotten even more powerful and simple to install.
As part of the site is password-protected then at a minimum I’d still need two files, one coming in at 15MB and the other 56MB. It was the size of the latter that made me split it further as I’d hate to lose the whole file due to some glitch.
One thought I did have was to edit the sss-data.js files that the Simple Site Search creates and copy all the page data into one file. The main drawback of this, if it could work, would be I’d have to keep uploading the edited file as I guess it’d be overwritten each time I upload the site.
I suppose the other easy option could just be to run a ‘free page search’ and a ‘members page search’ alongside each other. I’ll also have a look at SPhider but that could be a bit above my ability level.
I have a very large website that I have split over five Freeway files. I wanted to add the Simple Site Search action across this site but it seems to be restricted to working with only one Freeway file.
If you split your site into multiple documents, I don’t think that SSS can generate a combined index. It could create a separate index for each document’s worth of site, and if you structure your site so that the search within each “silo” makes sense, then you could probably get along with this. But you might need to reconsider splitting the site if you want to use SSS for your search.
Remember that Freeway caches any files you add to the pages – images,
primarily – inside the Freeway document file, as a last-ditch backup
in case the original is lost or damaged. This can swell the document
to considerably larger file size than you’ve described here.
If I recall correctly, the Softpress.com document was over 100MB when
I worked on it, and that was only about a hundred pages. It made for
some rather slow open and save moments on the hardware of that era,
but the actual work went pretty well and I never (knock on wood) had
any issues with document corruption.
I know I’ve heard of Freeway documents being over 300MB, and I’m sure
the support folk can tell some tales about that, particularly when it
comes time to send them one such for diagnosis.
Walter
On Feb 25, 2011, at 9:03 AM, Gordon Low wrote:
As part of the site is password-protected then at a minimum I’d
still need two files, one coming in at 15MB and the other 56MB. It
was the size of the latter that made me split it further as I’d hate
to lose the whole file due to some glitch.