We get it all the time... its due to files being locked / accessed on
the webserver which the ftp is occurring.
On 16 July, 00:29, markus giesen markus.gie...@gmail.com wrote:
The weird thing is, that it is not a permanent error.
It shows up every now and then.
On 15 Jul., 04:18, Rob Palmer
Hello all,
I want to use some PreExecute Code or RenderTag in a PageTemplate to
prevent a part of the template of being published, if the Filename of
the published file does not match a certain extension. I tried
different things to have this work, but every single try failed with
the same
Have you used reflector to see if there is any hidden rql methods which
might help?
On 16 July 2010 13:30, Daniel daniel.h...@buerkert.com wrote:
Hello all,
I want to use some PreExecute Code or RenderTag in a PageTemplate to
prevent a part of the template of being published, if the Filename
Sorry, Tony, I am not experienced using RQL. Can you give me a hint?
On Jul 16, 2:33 pm, Tony Gayter tonygay...@googlemail.com wrote:
Have you used reflector to see if there is any hidden rql methods which
might help?
On 16 July 2010 13:30, Daniel daniel.h...@buerkert.com wrote:
Hello all,
Hi Daniel,
Sounds similar to the issue we had with image placeholders, we would
just get the GUID out, as we were doing it all in pre-execute, turns
out it was too early in the page lifecycle to grab the information, so
we switched to an attribute placeholder to get the file name of the
image,
The best way I found for me is to disconnect the pages from the list
and reconnect them.
--
You received this message because you are subscribed to the Google Groups
RedDot CMS Users group.
To post to this group, send email to reddot-cms-us...@googlegroups.com.
To unsubscribe from this group,
Richard ... in the end, way to complicated and not worth the measly
return in functionality for all that work. Any other ideas? At this
point, I have decided to do it through LiveServer until / unless I can
come up with a CMS solution.
- mbyisrael2
--
You received this message because you are
Hi everyone,
I have a target dynament which tests the value of the content
attribute publishedDate against a request parameter:
rde-dm:target group=HTM include-mode=content-info
rde-dm:constraint
content.publishedDate ge
[#request:dateOfLastQuery#1970-01-01#]
/rde-dm:constraint
Hmmmthat strategy might help. It will be a lot of work to signal
out the pages, and the process isn't flawless, but it's certainly
better than no solution.
Thank you.
On Jul 16, 11:43 am, Timo Zimmermann zimmermann.t...@googlemail.com
wrote:
the user may only find pages which they may read.
Tiffany, what about using the rde-dm:query searchable=false/
true.../rde-dm:query element? I copied the following straight
from the LS Dynaments manual:
In additional Query DynaMents, you can use the special parameter
searchable=[true|false] to prevent particular content areas from
being indexed
10 matches
Mail list logo
