Comments on: More info on restricted post hack

By: Cathy

Cathy — Tue, 30 Nov 1999 00:00:00 +0000

I added this code to my main index page, and now all of a sudden the left sidebar with the calendar, links, etc is showing up at the bottom of my page. Any ideas on why this would happen?

By: Jean

Jean — Tue, 30 Nov 1999 00:00:00 +0000

I'm having a similar problem to Cathy's. When I add the code, my right sidebar moves to the bottom-left corner of the page.

Also, when I click on the link to enter a password, I get taken straight to the entry without having to input any password. Please help.

By: Jennifer

Jennifer — Tue, 30 Nov 1999 00:00:00 +0000

The way these samples are set up is that you have to go to the individual entries page to view the restricted post via password (see the template on the original post here)
The template shown in THIS post shows the MAIN INDEX page (where as the other shows indiviual entries page with the password access)

Are you asking for a template for the MAIN INDEX page that allows for password access?

By: C.

C. — Tue, 30 Nov 1999 00:00:00 +0000

I'm having some trouble getting the script up and running. I've double and triple checked the script against this one, and I don't see anything different between what I'm putting onto my site from what's here, but I'm having a weird sort of problem…

Instead of showing up only on "restricted" posts, I'm getting pieces of code spit out into every entry; it looks something like this:

damn job. To gain access via password click here
"; } else { print <<entry text here
11:22 AM | comments - 0 | Trackback - 0
EOF; } ?>

When I tried making a test post in the restricted category, I got the same thing. It won't display the "send email for access" message.

Could anybody think of something that would be causing this?

(I removed the code from my site for now, since it looks silly to have bits of code sticking out. If anyone would like to take a look at it, let me know.)

Thanks!

By: Jean

Jean — Tue, 30 Nov 1999 00:00:00 +0000

Okay, I figured out why the CSS was wonky, but I'm still unsure about the password input…

By: Jennifer

Jennifer — Tue, 30 Nov 1999 00:00:00 +0000

Did you install the script on your individual archives template?

By: Maggie

Maggie — Tue, 30 Nov 1999 00:00:00 +0000

As far as the "FORM EMAIL INSTRUCTIONS:" go, does anyone have the code for "(you can make this a popup later on using normal javascript popup commands)"? Also, in the CLICK HERE TO REQUEST ACCESS. part of the code, where it says href=\"#\", how would that look after it is filled in? Something like href=\"http://www.yoursite.com/pathto/form.php\"? Sorry for repeating part of this. I was thinking the reason no one has replied to my previous comment was because I had been unclear. I would really appreciate your help with this. Also, is there a way to keep the comments private as well. In a test entry for the restricted entry, if you were to go here, you can see the comments related to the restricted entry.

By: Crys

Crys — Tue, 30 Nov 1999 00:00:00 +0000

Does anyone know of a way to prevent restricted entries from being viewed in archives and the search function, using this hack?

By: Jennifer

Jennifer — Tue, 30 Nov 1999 00:00:00 +0000

Just posted this same response on another related post, but I'll copy/paste:
The script needs to be put on every archive template that displays your post. So that means your main index template, individual archive, monthly and or category archives. Anything that displays the body and/or extended entry of your posts.

By: Ria

Ria — Tue, 30 Nov 1999 00:00:00 +0000

Thanks for the wonderful script Jennifer. XD I was able to get it working but I do have one issue. When visitors request access via e-mail, the subject header is missing the cookie id.

Example: mailto:princesa_riaAThotmail.com?subject=access_for__and_01.2.3.04.05

But when they refresh the site, the cookie ID becomes visible. Also, when I use the pop-up form to test it I receive the following in the body of the e-mail:

Name: Ria
E-Mail: princesa_riaAThotmail.com
IP and COOKIE ID:

Any help will be appreciated. Thanks!