Has eTemplate a cache file or temporary file?

Marcel_Bariou 2008-03-12 09:08:32 UTC #1

Hello Everybody
I’am discovering eTemplate through the RalF Becker / Klaus Leithoff tuto. As sometimes I make several mistakes in my template build, I’m totally enable to remove some widget through the eTemplate Popup. So I want to remove this widget from the XML file manually.

But when I try to do that in th e*.xet file in my application, I remove the element from the *.xet file but each time this file is rebuilt automatically with this widget I want to remove. My question is : have you a temprary file file, a cache file or something like that and where it is ?

You can tell me to have a better usage of the eTemplate popup builder, but as the documentation is not completed enough for each widget, I want to know what I’m doing exactly and this XML file seems to be the best place.

Thanks for your help or advices

Marcel

Marcel_Bariou 2008-03-12 10:39:49 UTC #2

Answer to myself => each template is registered in the database in the table egw_etemplate, with its name test.page (for the PAGE page template of APPLICATION test). When you remove this record you remove the template, so you have to rebuild it from the page.xet in the template/default directory of your application…

Marcel

Marcel Bariou:

Hello Everybody
I’am discovering eTemplate through the RalF Becker / Klaus Leithoff tuto. As sometimes I make several mistakes in my template build, I’m totally enable to remove some widget through the eTemplate Popup. So I want to remove this widget from the XML file manually.

But when I try to do that in th e*.xet file in my application, I remove the element from the *.xet file but each time this file is rebuilt automatically with this widget I want to remove. My question is : have you a temprary file file, a cache file or something like that and where it is ?

You can tell me to have a better usage of the eTemplate popup builder, but as the documentation is not completed enough for each widget, I want to know what I’m doing exactly and this XML file seems to be the best place.

Thanks for your help or advices

Marcel

Nathan_Gray-2 2008-03-12 14:11:45 UTC #3

Answer to myself => each template is registered in the database in
the table
egw_etemplate, with its name test.page (for the PAGE page template of
APPLICATION test). When you remove this record you remove the
template, so
you have to rebuilfd it from the page.xet in the template/default
directory
of your application…

Ralf, correct me if I’m wrong, but…

Each etemplate is stored in the database, as you have discovered.
When you click ‘Dump for setup’ in etemplate, all the templates for
your application are dumped to your_app/setup/etemplates.inc.php.
This is the file you use when distributing your application to
distribute all your templates as well. When this file changes, the
database is updated from it.

The template/default/ xml files generated when you ‘Export XML’ are
not really used, but they can give you a good idea of what’s going on
in your eTemplate.

Nathan Gray
nathan at goarctic dot com

Extra punctuation??? Ug!!!
Just say no! Punctuation marks do not gain significance if you
increase their number, they make you look silly. One is sufficient.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Marcel_Bariou 2008-03-12 18:00:14 UTC #4

Thanks Nathan,
I think your are totally right After several reading I’ve discover exactly what you are saying. But it take me a while to understand the path and hierarchy in eTemplate I think I’m OK now, mainly xith Grid and GroupBox.

Interesting you give me an answer, because I’m digging here to understand pERP and eGroupware of course. Are you always active on pERP ?

Thanks for your help

Marcel

Nathan Gray:

On 12-Mar-08, at 4:39 AM, Marcel Bariou wrote:

Answer to myself => each template is registered in the database in
the table
egw_etemplate, with its name test.page (for the PAGE page template of
APPLICATION test). When you remove this record you remove the
template, so
you have to rebuilfd it from the page.xet in the template/default
directory
of your application…

Ralf, correct me if I’m wrong, but…

Each etemplate is stored in the database, as you have discovered.
When you click ‘Dump for setup’ in etemplate, all the templates for
your application are dumped to your_app/setup/etemplates.inc.php.
This is the file you use when distributing your application to
distribute all your templates as well. When this file changes, the
database is updated from it.

The template/default/ xml files generated when you ‘Export XML’ are
not really used, but they can give you a good idea of what’s going on
in your eTemplate.

Nathan Gray
nathan at goarctic dot com

Extra punctuation??? Ug!!!
Just say no! Punctuation marks do not gain significance if you
increase their number, they make you look silly. One is sufficient.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Nathan_Gray-2 2008-03-12 18:09:20 UTC #5

…
Interesting you give me an answer, because I’m digging here to
understand
pERP and eGroupware of course. Are you always active on pERP ?

Yes, working on pERP is my full-time job.

Nathan Gray
nathan at goarctic dot com

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Ralf_Becker_6 2008-03-12 18:54:39 UTC #6

I can not say it any better

Ralf

Nathan Gray schrieb:

Answer to myself => each template is registered in the database in
the table
egw_etemplate, with its name test.page (for the PAGE page template of
APPLICATION test). When you remove this record you remove the
template, so
you have to rebuilfd it from the page.xet in the template/default
directory
of your application…

Ralf, correct me if I’m wrong, but…

Each etemplate is stored in the database, as you have discovered.
When you click ‘Dump for setup’ in etemplate, all the templates for
your application are dumped to your_app/setup/etemplates.inc.php.
This is the file you use when distributing your application to
distribute all your templates as well. When this file changes, the
database is updated from it.

The template/default/ xml files generated when you ‘Export XML’ are
not really used, but they can give you a good idea of what’s going on
in your eTemplate.

Nathan Gray
nathan at goarctic dot com

Extra punctuation??? Ug!!!
Just say no! Punctuation marks do not gain significance if you
increase their number, they make you look silly. One is sufficient.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

–
Ralf Becker
eGroupWare Training & Support ==> http://www.egroupware-support.de
Outdoor Unlimited Training GmbH [www.outdoor-training.de]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 (0)631 31657-0

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers