This German Article is related (i think, but I'm not german): http://www.typolight.org/board/topic/2579.html

I have a problem, I want to keep my existing Flash site on my site, and its easiest to keep the existing XML input files, e.g. bg.xml (for backgrounds), design.xml (for design client list), etc. in the root of the site.

Unfortunately, I'm not sure when, but TL seems to be deleting my XML files. Leo any ideas on what's going on.

It would be best if I move the content to a sub-folder instead, e.g.
http://www.site.com/flashsite/

so TL won't delete these files?

Here is the translation of the relevant answers by Leo:

What files does TYPOlight delete from the root?

Quote:

TYPOlight deletes from the root all XML and CSS files, which are not linked in the DB (e.g. created by TYPOlight itself). Such files are News Feeds, Calendar Feeds and all Stylesheets.

Why does TYPOlight do that, and where shall I store other files?

Quote:

TYPOlight knows only what Files it has created itself [what files currently should be there]. To avoid outdated or allready deleted CSS or XML files to stay, TYPOlight therefore deletes all files that are currently not linked internally. If you want to use other XML/CSS files, you can store then in the templates folder.

Personal note: Any other subdirectory should also be ok, since TL only wipes the root IMHO.

So if I develop a Google Sitemap Module that renders an XML file in the root, then that will also get deleted? Maybe Leo can integrate a Google XML file in the root (sitemap.xml -- using the sitemap standard) in version 3.0. This greatly enhances the index-ability of a site.

Some member reported in that thread that he is storing his google sitemap in the root, but with extension .txt instead of .xml and it seems to work without problems.

It would be nice to have this as a module in TL, don't you agree? Thanks for the feedback.

Hi guys,

you can already create a "sitemap.xml" file in the root folder which will not be deleted. From the next version (2.5.1), TYPOlight will not touch any XML files that start with "sitemap" anymore (so you can e.g. create "sitemap_domainA.xml" and "sitemap_domainB.xml").

Regards
Leo

I am having this problem with Typolight 2.5.9.

It's deleting my crossdomain.xml file everytime from the root and I need it there for slideshowpro to run.

Says it's fixed in 2.5.1 but seems that at this latest release is not!

I need urgent help on how to avoid this. Any hints?

leo:

TYPOlight will not touch any XML files that start with "sitemap" anymore (so you can e.g. create "sitemap_domainA.xml" and "sitemap_domainB.xml").

Crossdomain does not start with "sitemap", does it?

I know there is a solution, but I do find it anymore ...

unless it was for css files...

To stop files being deleted in the root directory, you can add them to the dcaconfig.php file like so:

$GLOBALS['TL_CONFIG']['rootFiles'][] = 'filename_not_to_be_deleted.xml';

these can be any files not just xml files.

With regards to sitemaps being deleted, I have requested the system be a little bit smarter, see...

http://www.typolight.org/forum/topic/6942.html

regards,
David

Thanks David, that's exactly what I have forget

I just tried this code added to my dcaconfig.php with no success.

$GLOBALS['TL_CONFIG']['rootFiles'][] = 'filename_not_to_be_deleted.xml';

All my news feed xml files from the multifeed and a crossdomain.xml still gets deleted.. my event feed how ever stays where it should.
So tl deletes 4 out of 5 xml files.

i list them like in this manner:

$GLOBALS['TL_CONFIG']['rootFiles'][] = 'filename_not_to_be_deleted_1.xml';
$GLOBALS['TL_CONFIG']['rootFiles'][] = 'filename_not_to_be_deleted_2.xml';
$GLOBALS['TL_CONFIG']['rootFiles'][] = 'filename_not_to_be_deleted_3.xml';

I must be doing something wrong, can anyone tell me how to get it right?

many thanks

T

Some additional info. If im logging in to the backend and go to multifeeds then they reapear on my server.
This happends without actually going into one feed, so it happends without re-saving/eporting the feed/xml.

You have to store it in your localconfig.php.

Ok it said dcaconfig.php above..


Anyways many thanks Leo!!