X3Photo Gallery Forums

alexhenes wrote:I am having a tough time getting the following html to work when I place it in the folder content field in the site settings.

I am not quite sure what you mean the "folder content" field ... You could probably add additional html to the include.content setting in your page settings, although right now I am wondering if that might make it display before your actual page content and not after. Do you see anything at all on your website, even dead images?

alexhenes wrote:| <a href="www.bentgate.com" target="_blank"><img src="/banners/Snowsports.gif" width="980" height="120" border="0"></a>

the banners folder is in the root of my content folder

Regardless of the first factor, any src starting with /slash means the file will be looked for relative to the root of your domain regardless of X3. Therefore, if you have the banners folder in your content folder, the src should probably be like this: Also, just for reference, you should always use http:// in external links, or some browsers will consider the link to be relative to the current page path:<a

Any chance I can see the result? A bit hard to diagnose with no links to check how it is displaying, and why the image is not displaying ...

alexhenes wrote:To clarify... I a using the content field in global settings. Here is what I have right now...

In global settings, there are page.content settings, which ONLY apply if the page's own content is empty, and include.content, which appears BEFORE any content set in the page.

alexhenes wrote:In addition... including this html in the global site settings seemed to significantly slow down the loading of the site... to the point it wasn't really usable.

Including something into content (or changing it), basically means that X3 needs to recreate the cache- and templates for ALL your pages ... and you have a LOT of pages. Furthermore, I see you have preload:true on your website ... That is a combo that could make any server struggle for a while ... I would perhaps recommend you turn off the preload option until you are DONE editing the page for a good while.

Basically after including the html into your content setting, it is very much possible your pages may be slow for a short while, but as long as you have preload OFF for the time being, it is not possible that the pages would not speed up after a while as they get cached.

You need to remember, you might have many other visitors on the website at the same time you are editing ... That means while you are making changes, the entire cache gets flushed, and depending on how many simultaneous visitors you have, your shared server may be trying to re-create pages for dozen of simultaneous requests. Add the preload option into that, and it would definitely cause havoc.

Another reasons why we recommend enabling the preload option some time AFTER editing, is because the preload builds a huge data-file from all pages. If those pages are already "processed" and cached (by being visited and navigated in ajax mode), the preload option only needs to loop through the already-processed templates, which is less demanding. If you are setting the preload on before pages are visited(and cached), it means it has to loop through ALL your pages and process them in one go. Imagine if several visitors make the request for this file at the same time.

Where did you get that corrupted code from src="img scr="/ ... ???

I corrected it, and it works now http://merelyafleshwound.com/Road-Biking/Utah/

alexhenes wrote:also... notice that the site performance is pretty sluggish... bring up the site and then click on Mountaineering or one of the sections below it.

When I tried earlier, it seemed sluggish ... when i try now, it seems pretty good:
http://merelyafleshwound.com/Road-Biking/Utah/

Not bad considering all the resources it is loading up front and the amount of images:

alexhenes wrote:also... with respect to preload... and setting it back to true... when you say to set it to true once done editing for a 'good while'... do you mean hours w/o editing, days, should I wait until the beta is done and I pretty much have most changes and tweaks in place?

My only points in regards to this is: 1) It is so important that you remember to disable it if you are going to do some editing, and that is why you should be very conscious about enabling it "willy nilly". If you "forget" to disable it while editing, your server would be overloaded with unnecessary tasks ... basically 1 page loads would say "please process this page, oh and process the other 100 also!". 2) Sometimes, after editing, it is better that your website has been browsed through (by you or someone else), so that single-page cache files are created, before the entire site is requested in a single load ...

However, nothing wrong with setting preload:true after you are editing for the day, although your website might become very sluggish for anything from 1-10 minutes ... At some point though with heavy content, it might even create a timeout on your server ...

The preload option is pretty cool, but I guess we still need to label it as "experimental", especially since we don't currently have any automation in place that can control the preloader state.

We could easily have an "empty cache" button, but re-build cache would be complicated as it's tied in with the actual creation of the template that is related to the specific request. Also, the requests are more than plain pages ... It is the json outputs used for ajax, and custom element requests also. Furthermore, images are resized and scaled based on the layout of the page, and the device that is viewing them, and it would not be plausible pre-cache all your images in one go ... certainly not for multiple sizes.

We can think about it ...

good idea!