[VodkaFish]

While on my journey from 3.6 to 3.7 I'm having some trouble with a script I have that looks at some extra checkboxes below a post.

In the newpost_process hook I take $post['message'] and parse it for a variety of things based on the checkboxes below the post.

So I'd have this in my template:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Then in the hook I'd have:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Checked off or not, I'm never getting within that if statement. If I can't use $post['parsethis'] what can I use to see if parsethis was checked off?

[Opserty]

The users have to "submit" the form, it won't just run the code automatically when you tick the box.

Note: Including forms inside posts, will cause conflicts with the inline moderation form (the one that allows you to check the boxes in the corner of a post). That is if you are a user with inline moderation permissions.

[VodkaFish]

I'm sorry, I didn't explain what I was doing properly.

This is a checkbox I've added to the misc area for when you make a new post, right under "Automatically parse links in text" that all vB new posts have. It's not a form within a form, just an additional input field.

[Opserty]

Oh, I see. You need to clean the input ( Using the vBulletin Input Cleaner) from the checkbox. TYPE_BOOL will probably be the one you want. Then you check it like so:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

[VodkaFish]

The odd thing is if I put print_r($post) in the newpost_process hook, I see everything in the $post array, and [parsethis] is nowhere to be found. For some reason the field is not being submitted.

[Opserty]

Use the information I gave you in my previous post, you could just add it to $post yourself...

If you want to see what vBulletin is doing with your code, start with the form submission. (Look at where the form posts too, you can find it by looking at the HTML code for the form.) Follow it through the relevant PHP files and see what vBulletin is doing to it.

Most likely the following files will be appropriate:

newreply.php
newthread.php
functions_newpost.php

[VodkaFish]

Originally Posted by Opserty

Use the information I gave you in my previous post, you could just add it to $post yourself...

That's what I'm trying to do, or should I say that's what I was doing previously. $post would just include any input field I added to the form in the newthread template. I assume I need to do something in the hook I'm using (newpost_process) or another one that gets hit first. I tried to "clean" it, but it's not even being passed along to clean, so obviously vbulletin is ignoring the field - where can I tell it to look for it?

(thanks for your help so far)

[Opserty]

$post is a variable used within a function... you need to clean it and pass it to the function using another hook. It won't look for it, you need to do the same thing vBulletin does to the other variables.

I think instead of my trying to explain it, it would just be easier to look in the PHP file, follow it from where the form has been submitted.

[VodkaFish]

Yeah, I just have to figure out how to pass it. In 3.6.x it was passed automatically.

--------------- Added 22 Aug 2008 at 01:02 ---------------

Ok, ok. A cleaning was all that was necessary, and then I was able to access it (just using the method you did above).

Sample for those reading this:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Using $vbulletin->GPC['parsethis'] instead of $post['parsethis'] is no big deal, just a few search and replace changes.

Thanks again for the help.