Textpattern Support Forum

I think of a way to delete an article from the write/edit page of each article.
A button after “Reset time to now” …

—> “DELETE”
(I’ve post a request in the features request forum).
I don’t have any idea of the difficulty to do this, it is just a suggestion (honestly I am sure that others already thought of it. Thus that should not be so easy to make…).
It would have sense with the front-editing concept.

wouldn’t it be just as useful and much simpler for a plugin to use textpattern’s own cookie?

I was asked today why one needs to set an extra cookie for this and was stumped for an answer, particularly as the “edit” link depends upon you being logged in.

Would it be possible to make it use the ‘remember me on this machine’ cookie txp sets when you’re logged in or not?

BTW: as “The Exit” said, you need to give rights to lower user-levels to show the extension tab. This is no problem, unless you have other extension tab plug-ins which should not be available to all.

wordgasm wrote:

how come it wouldn’t work on my site? I’ve set the cookie and followed the instructions, even checked and rechecked the template and the article form, but it wouldn’t work? =/

It would help if you showed us what your relevant template and form code is.

By the way, you did turn the plugin on, right?

Last edited by Destry (2006-07-30 16:21:20)

I see two things worth considering:

1. Divitis in affect (use of more divs than necessary). Maybe start by simplifying your code, dropping unneeded divs and using other selectors where appropriate (e.g <code><h1></code>, <code><h2></code>, <code><h3></code>, whatever).
2. I think the plugin tag, <code><txp:rss_article_edit> … </txp:rss_article_edit></code> is supposed to be tied to an actual article body that is under Textpattern’s control. I don’t see an actual <code><txp:body /></code> in your code. You’re using another plugin tag for the body and that’s not how the “edit” plugin was designed.

Here’s one idea about redoing that form (CSS not included):

<code><a href=”<txp:permlink />” title=”<txp:title />”><h1><txp:title /></h1></a></code>
<code><txp:body /></code>
<code><div id=“comment”><p><txp:rss_article_edit>edit</txp:rss_article_edit> <txp:posted format=”%d.%m.%y | %R” /> | <img src=”/blue/comment.gif”></code> <code><txp:comments_invite /></p></div></code>

Ultimately you can do what you like with the divs, but I think the <code><txp:body /></code> tag is the root of the real problem here. Just a guess.

Last edited by Destry (2006-07-31 18:38:48)

Sorry, this line should have been written like this…

<code><h1><a href=”<txp:permlink />” title=”<txp:title />”><txp:title /></a></h1></code>

(header tags on the outside of the anchor)