lgutman
asked on
Keeping Custom Tags seperate by application
I am building a set of boxes that will house ColdFusion applications. These will be running on ColdFusion MX enterprise. Each application can have a directory inside of it with custom tags. Is there a way to keep to keep each application using its own custom tags? I have tried sandbox security, but it does not appear to work.
Thanks
Larry Gutman
Thanks
Larry Gutman
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Do you have to create a custom tage path to each application for this to work?
ASKER
Do you have to create a custom tage path to each application for this to work?
Q). Do you have to create a custom tage path to each application for this to work?
A). Nope
I use the method of saving my custom tags in the root folder of my applications. Because my server requires me to email them to set them up, so I just keep them in my applications root folder. Then if I'am inside that root i call it <cf_TAG> but if I'am inside another folder I then use <cfmodule and pass any attributes the tag needs just like the cf_tag call.
A). Nope
I use the method of saving my custom tags in the root folder of my applications. Because my server requires me to email them to set them up, so I just keep them in my applications root folder. Then if I'am inside that root i call it <cf_TAG> but if I'am inside another folder I then use <cfmodule and pass any attributes the tag needs just like the cf_tag call.
2 lgutman.
No. No path needed in this case. You just can try it and see it works.
No. No path needed in this case. You just can try it and see it works.
All the above is very messy
In a hosting envoirment prefixing the custom tags relating to the application / domain was more suited and aided in stopping unsual actions
so in your customtag folder you have
<customtags>
<appplicationname_1>
<cf_applicationname_1_tagn ame>
<appplicationname_2>
<cf_applicationname_2_tagn ame>
In a hosting envoirment prefixing the custom tags relating to the application / domain was more suited and aided in stopping unsual actions
so in your customtag folder you have
<customtags>
<appplicationname_1>
<cf_applicationname_1_tagn
<appplicationname_2>
<cf_applicationname_2_tagn
demarco - i didnt get what ur trying to say here
can u pls explain it in a bit detail [if u dont mind]
K'Rgds
Anand
can u pls explain it in a bit detail [if u dont mind]
K'Rgds
Anand
Sorry
ok from the top
You have your custom tags folder - yes
IN that folder you have additonal folders for each application ( not client root )
IN each Application folder under the customtag folder you have your custom tags for each application
Each Custom tag should be named in relation to the application that calls it
ie <cf_applicationname_tagnam e>
that way you can have multiple custom tags talored to each application with out the need to have customtag paths for each app ..
this offers a basic level of protection to ensuring each application doesnt have mixups on custom tags if a client or app developer alters a custom tag for a particular app and then resulting in other apps breaking down
Of course you can still have you top level Ctag flolder with the generic custom tags you might want to host
(ie fuzebox etc )
I hope that makes it clearer ?
ok from the top
You have your custom tags folder - yes
IN that folder you have additonal folders for each application ( not client root )
IN each Application folder under the customtag folder you have your custom tags for each application
Each Custom tag should be named in relation to the application that calls it
ie <cf_applicationname_tagnam
that way you can have multiple custom tags talored to each application with out the need to have customtag paths for each app ..
this offers a basic level of protection to ensuring each application doesnt have mixups on custom tags if a client or app developer alters a custom tag for a particular app and then resulting in other apps breaking down
Of course you can still have you top level Ctag flolder with the generic custom tags you might want to host
(ie fuzebox etc )
I hope that makes it clearer ?
ok - so its just the naming of the tags that needs to be done in a specific manner ?
also just to confirm
customtags folder in C:
application1
also just to confirm
customtags folder in C:
application1
-customtags folder in C:
-application1
-all tags fo application 1 under this folder with names starting as "?????"
-application2
-all tags fo application 1 under this folder with names starting as "?????"
pls confirm !
K'Rgds
Anand
-application1
-all tags fo application 1 under this folder with names starting as "?????"
-application2
-all tags fo application 1 under this folder with names starting as "?????"
pls confirm !
K'Rgds
Anand
Yup thats the idea
what will be the name of the file that will be written as custom tag [above indicated as "?????"]
so lets say i have a tag with file name as "anandkp.cfm"
then in this case - how shld it be named ???
so lets say i have a tag with file name as "anandkp.cfm"
then in this case - how shld it be named ???
<cf_THENAMEOFTHEAPPLICATIO N_anandkp>
ASKER
This is the most logical answer for what I am trying to accomplish.
Thanks everyone for all your insight. I hope Macromedia does some work on this in the future. I was hoping the Sandbox security with the Enterprise edition would cover this but it doesn't.
Thanks everyone for all your insight. I hope Macromedia does some work on this in the future. I was hoping the Sandbox security with the Enterprise edition would cover this but it doesn't.
er .... ok ?
hi there,
just to make sure things r set right for people who r reading this !
demarco - i tried ur suggestion - but i cldnt get thru with <cf_THENAMEOFTHEAPPLICATIO N_anandkp>
the name of applicaiton here is "the name set in the application.cfm file - with CFAPPLICATION tag - right ??
but i still cldnt get it to run on CFMX
here is what i cld find in its help section:
Storing custom tag pages
You must store custom tag pages in any one of the following:
The same directory as the calling page
The cfusion\CustomTags directory
A subdirectory of the cfusion\CustomTags directory
A directory that you specify in the ColdFusion Administrator
To share a custom tag among applications in multiple directories, place it in the cfusion\CustomTags directory. You can create subdirectories to organize custom tags. ColdFusion searches recursively for the Custom Tags directory, stepping down through any existing subdirectories until the custom tag is found.
You might have a situation where you have multiple custom tags with the same name. To guarantee which tag ColdFusion calls, copy it to the same directory as the calling page. Or, use the cfmodule tag with the template attribute to specify the absolute path to the custom tag.
K'Rgds
Anand
just to make sure things r set right for people who r reading this !
demarco - i tried ur suggestion - but i cldnt get thru with <cf_THENAMEOFTHEAPPLICATIO
the name of applicaiton here is "the name set in the application.cfm file - with CFAPPLICATION tag - right ??
but i still cldnt get it to run on CFMX
here is what i cld find in its help section:
Storing custom tag pages
You must store custom tag pages in any one of the following:
The same directory as the calling page
The cfusion\CustomTags directory
A subdirectory of the cfusion\CustomTags directory
A directory that you specify in the ColdFusion Administrator
To share a custom tag among applications in multiple directories, place it in the cfusion\CustomTags directory. You can create subdirectories to organize custom tags. ColdFusion searches recursively for the Custom Tags directory, stepping down through any existing subdirectories until the custom tag is found.
You might have a situation where you have multiple custom tags with the same name. To guarantee which tag ColdFusion calls, copy it to the same directory as the calling page. Or, use the cfmodule tag with the template attribute to specify the absolute path to the custom tag.
K'Rgds
Anand
.. er thats what i said
I was giving your a naming convention Im sory if your didnt follow
I was giving your a naming convention Im sory if your didnt follow
yeah sorry if i am bothering u
but i was just trying to understand - if i was missing something - in the way i tried to do thigns, as per ur suggestions.
thanx for ur help !
Cheers
Anand
but i was just trying to understand - if i was missing something - in the way i tried to do thigns, as per ur suggestions.
thanx for ur help !
Cheers
Anand
Say, you have a custom tag <cf_showdata>. Your first application is in /first/, the second is in /second/.
You place your custom tag named showdata.cfm to /first/.
Now if you refer to <cf_showdata> in application in /first/ it will work, but if you try to use <cf_showdata> in /second/ it will not work.