Hi TYPOlight developers,

I have just released version 2.6beta. Please read the announcement and the changelog and check whether your third party extensions run on it. If you have any questions, please post them here.

http://www.typolight.org/archive/items/t…polight-2_6beta.html

Regards
Leo

P.S.: Since it is a beta version, it is not available via live upate.

This is great, Leo! Thanks! I especially like the new insert tags feature, great!

Forgive me it I am overlooking something obvious, but how exactly can I get pages to cache?

Looking into system/html, it seems only images (jpg, gif) do get cached.

What I did to try is the following:

- Always logged out from front- and backend for each test
- Assigned a cache timeout to the root page "Music Academy" assuming that the setting would propagate to child pages, but no luck.
- Assigned a cache timeout to individual pages, but also no luck.

Hi Acenes,

cached pages are stored in system/tmp (system/html is world readable).

Regards
Leo

Seems of the whole Music Academy sample, only these two pages get cached:

- The Academy - Teachers - Helen Lewis / Read More...
- The Academy - Teachers - James Wilson / Read More...

What conditions need to be met to make a page get cached, besides the cache timeout in site structure?

Hi Acenes,

you must not be logged in at all (neither back end nor front end) and assign a cache timeout value in the site structure. Then, open each front end page once and check your tmp directory.

On my system, 11 pages are being cached.

Regards
Leo

I made sure settings are right:

- Assigned 7 days to the root page "Music academy" and all child pages to inherit the settings.
- Then in maintenance, select all and clear cache.
- Logged out from frontend and backend.
- Visited all pages in the frontend as guest.

Now 4 pages got cached.

Logged into backend again, and did maintenance / rebuild search index.
Now another 4 pages are cached which I may have missed, makes a total of 8.

Now just for joy I cleared the caches again and rebuild the search index - 4 pages get cached by doing so.
Logged out from backend and visited pages on the frontend - no other pages got cached.

Some other issue: The go back links seems to be broken.

Going to The Academy - Teachers - Helen Lewis / Read More.., and then clicking on "Go back" always bring me to the page "Navigation", no matter where I came from.

Hi Acenes,

please check against the online demo. It seems to work there (both issues).

Regards
Leo

Hi Acenes,

I have just updated typolight.org because it contains a lot of cached pages. It works there as well.

Regards
Leo

Hi Acenes, hi Leo,

no Problem in backlinking on my test environment

Stefan

The reported issues are result of a combination of browser cache and cookies. After clearing all cookies and the browser cache, everything seems to work as it should. Page caches then get built again. After clearing the TL cache, it will hovever not get rebuilt until one presses Ctrl+F5 to force reload of the page.

The back link issue could be a special case because I have different installations on the same domain. So when you for example have one installation of TYPOlight in www.example.com and another in www.example.com/subpage, the one in subpage will get also cookies that were created and ment for the installation in the upper folder. This is a basic issue of the way PHP handles $_COOKIE, and ATM I don't see a way how we could avoid it.

From the manual of setcookie():

Quote:

The path on the server in which the cookie will be available on. If set to '/', the cookie will be available within the entire domain . If set to '/foo/', the cookie will only be available within the /foo/ directory and all sub-directories such as /foo/bar/ of domain . The default value is the current directory that the cookie is being set in.

Hi guys,

Russ McRee has discovered an XSS vulnerability of the beta version, so make sure not to use it on a live server! The issue does not affect any previous versions of TYPOlight. If you want to fix it on your beta installation, please follow these steps:

1. Open system/libraries/Environment.php and change line 385

Code:

$this->arrCache['request'] = urldecode($strRequest);

to

Code:

$this->arrCache['request'] = $strRequest;

2. Open system/modules/frontend/Frontend.php and change lines 108 to 113

Code:

for ($i=1; $i<count($arrFragments); $i+=2)
{
	$_GET[$arrFragments[$i]] = $arrFragments[$i+1];
}

return strlen($arrFragments[0]) ? $arrFragments[0] : null;

to

Code:

for ($i=1; $i<count($arrFragments); $i+=2)
{
	$_GET[urldecode($arrFragments[$i])] = urldecode($arrFragments[$i+1]);
}

return strlen($arrFragments[0]) ? urldecode($arrFragments[0]) : null;

Again, this issue does not affect any other release than version 2.6beta!

Regards
Leo

HI

where can I find the template for the sign telling you that you are logged in in the backend? For now I have deleted the include in the fe_page-template because it destroyed my design, the background was moved downwards and some other things were ridiculous.
I would like to make that message static so that it always stays on top, even if you scoll down the page and that the content slides behind it.

seaneble

Hi seanable,

the default message is built in system/modules/Frontend.php. You do not need to change it, though. You can easily build a custom reminder by adding the following to your template:

Code:

<?php if (BE_USER_LOGGED_ID): ?>
<div>My custom reminder</div>
<?php endif; ?>

Regards
Leo