Hi Mark,
Sorry for be so verbose.
If you are working with multiple apps on your laptop, you need to make sure
that you are working with the correct custom
tag directory for the app you are working on. When you used the setup wizard,
Plum asked you to set up a custom tag
mapping in the CF Administrator (Extensions/Custom Tag Paths), that would point
to the custom tag directory for that
project. If you switch projects, you have to go into the CF Administrator and
change the custom tag mapping to point at
the custom tag sub-directory for that project.
This might be the culprit for why the search form range issue we messed with
last week isn't working for you.
What I have done myself is to create a 'Plum Library' out of a freshly generated project. I have placed it under
version control so that I can back out of any changes I make. I map the Custom Tags path in the CF Administrator to the
Plum Library/customtags directory and leave it alone. I make changes to the custom tags that will affect all apps in the
Plum Library only.
When I create a new project, I immediately delete that project's customtags subdirectory. Since the library customtag
path is the only one mapped, CF will use that path. So all new projects use the same custom tags library.
While in development mode, my project names always have a '_dev' suffix on
them, so I can differentiate them from a
production app (no suffix) that has been run through the CF_2CFMODULE utility.
At that time I add a copy of the library
custom tags subdirectory to the deployment app, and there is now no conflict
because all the tag calls in the app are
now cfmodule calls. So I always have two copies of a project, one in development ('sample_dev') mode and one in
production/deployment mode ('sample').
Occasionally you may have a project where you will want to make extensive changes to tag behavior, only for that
project. In this instance, it makes sense to just replace your local customtags directory with a copy from the library,
point the CF Admin custom tag path at that directory, and go for it.
The key here is that there is always only *one* custom tag mapping in CF Admin. So you either use one copy for all, or
change the path mapping each time you are working on a different project.
There are probably better ways to do this, but this is what I have found works best for me. When the Churvii come out
with the new auto-cf_2cfmodule utility, this will be even better.
v/r,
Jeff
Mark Fuqua wrote:
I have been making changes to some of the custom tags that ship with PLUM.
The changes don't seem to change anything. I don't know whether I want this
answer to be yes or no. If the answer is no, it's no help. If the answer
is yes, it would help explain the problems I have been having, but will make
feel really dumb for not thinking of this sooner.
If I have several PLUM projects on my development computer (my laptop), does
that give me the same problems that occur in a shared hosting environment?
Is it possible that I am changing one copy of a custom tag and Coldfusion is
using one of the other copies from another project, rather than the one I
changed?
thanks,
Mark
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
