Serendipity Forums

hello,

another strange thing to serendipity_event_entryproperties:

Using a password protection to an article, seeing it on the article-list-page, I get the title of the article, the category, the author ... and the content of the first content form (body).

Looking at the sole articly I get NOTHING!

Of course, the purpose of password protection is, to see nothing without the pass. But really, completly nothing!? The page is nearly empty.

The body is known to everbody by the article-list, the title, the author and so one

Only the extended body is secret at this time, so IMHO all the known things can shown. And IMO the author, the title, the categories should be displayed!

Because the body-content is not secret, I think in most cases one would wrote something like "this article is about a secret thing X, so please type the pass. If you do not know it, ask the webmaster." This should be read on the article-view as well, I think.


Using a pass on a static page i get annother result:

I can see title and author, and a text ("Diese Seite ist Passwortgeschützt. Bitte geben Sie das geeignete Passwort ein:") (translated: page is pass protected, please enter pass.)

Hi!

The problem is in the API, if you allow the entry page to be viewn basically, all other plugins would be executed. But the purpose of password protection would be to not reveal anything else for a detailed entry. So technically, there's currently no way to get both things to work, because if you want to access the body on that page, you'd have to grant full access to the page.

HTH,
Garvin

hm, I try to understand, how the static page plugin does it.

Am I right, the pass-protection of static pages is a core part of the static-page-plugin. The pass protection of normal entries is part of the extended property plugin?

static pages seem to solve this problem by replycing the content of the <div class="serendipity_entry_body">-output.

Could this be a way for normal entries, too? filter the content of extended body and change it to something like "please enter the pass here: xxx"? So every other plugin would get this "new" content to work with?

I mean, all the other things - title, categories, author, body are no secret!

Hi!

stm999999999 wrote:hm, I try to understand, how the static page plugin does it.

The staticpage has its own handling, because the whole output comes from the plugin. In case of a blog entry, the whole output comes from the s9y core.

Am I right, the pass-protection of static pages is a core part of the static-page-plugin. The pass protection of normal entries is part of the extended property plugin?

That's right; the entryproperties plugin cannot have a full impact on the usual blog entry rendering, only in the important parts; but it cannot (or: should not) take over the full page generation.

Could this be a way for normal entries, too? filter the content of extended body and change it to something like "please enter the pass here: xxx"? So every other plugin would get this "new" content to work with?

Yeah, but that would mean that you could view other things on the detailed entry page, that you would normally not be allowed to. Like other plugins, comments, trackbacks etc.

I mean, all the other things - title, categories, author, body are no secret!

Yeah, but everything that also interfaces with a "detailed entry page". The password protection really applies to the article detail view, not only the extended body itself, because people could use the plugin capabilities to show content on the page that only executes, when the user has full access to the detail page.

Regards,
Garvin