Alan has asked how one gets a whole db,all users query based on an
indeterminate number of tags, (well actually he suggested two, but we
don't like the number two).
I have developed a query against our model, refined it, proposed a
de-normalisation to support retreiving tags as entry
The new branches are:
/roller/branches/roller_2.1
/roller/branches/roller_2.1_tagging
So...
- Final 2.1 fixes can occur in the roller_2.1 branch
- Tagging code can be committed in the roller_2.1_tagging branch
- And Roller 2.2 work can now commence in the trunk
- Dave
On Jan 30, 2006,
+1
I think that's a pretty well known best practice.
- Dave
On Jan 31, 2006, at 1:43 PM, Allen Gilliland wrote:
anyone opposed to the idea of moving our jsps inside of the WEB-INF
folder? i would create a new folder there called jsps, so the new
path would be /WEB-INF/jsps/website/* or
anyone opposed to the idea of moving our jsps inside of the WEB-INF
folder?
That's the best practice for JSP pages that users aren't supposed to target
directly from the outside. All sorts of reasons in favor, none opposed.
--- Noel
+1
On 1/31/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
anyone opposed to the idea of moving our jsps inside of the WEB-INF
folder?
That's the best practice for JSP pages that users aren't supposed to target
directly from the outside. All sorts of reasons in favor, none opposed.
I'll just continue to have this conversation with myself :)
I was looking at the proposals page and found this old proposal where
Dave pretty much layed out the same options I had listed, but with a
little more detail. Wish I had seen this sooner ...
currently we allow quite a few editors in the list of editors that comes
bundled in a default roller install ...
editor-ekit.jsp
editor-text.jsp
editor-dhtml.jsp
editor-text-js.jsp
editor-wiki-js.jsp
editor-rte.jsp
i'd like to trim down the list to maybe 2 or 3 good editors? there are
a few
