Drupal 6.x

Hi,

(d6.28)

I have a content type that requires authenticated users to pay to publish a node. However, on saving/paying/publishing the node, it is not viewable by the user -- but is "published"...

What I've noticed:

* Table 'node' in DB shows status 1 (published) for the given content after saving.
BUT...
* URL alias is not generated.
* After saving, if user tries to visit node via internal path (e.g. node/1961) it results in page not found. This is even though DB shows status=1.
* Admin can view the node (via internal path) and see it in views. But author (authenticated user) cannot.
However...
* Page is fully accessible if admin comes along and saves content (or changes status in some way), OR the author revisits the edit page and saves again.
* This only happens on the content type that requires payment.

Can anyone tell me what else needs to be present in the database for a piece of content to be "published" other than 'status=1' in the node table? I thought that if status was 1 it was published and an authenticated user would be able to view the content, but obviously there's some other condition that needs to be met which I'm missing.

I've posted a question at the site of the payment to publish module author, but absolutely no response (perhaps because it's d6 and they've moved on). So I'm hoping to fix it myself...

How do I add the check for questions
With the addition of a question directly field
Cousin of the applicable at this link

https://www.khanacademy.org/math/arithmetic/addition-subtraction/two_dig...

Thanks

Advertisement 6.x-2.2 module - I am having problems posting articles to Facebook. Instead of attaching the main image of the article to the post or no image, it's automatically attaching the tile ad images from the article page to the Facebook post. I'm wondering if anyone knows how to prevent this from happening. Recent changes in Facebook no longer gives the option to select "no image". We're also using the OpenPublish packaged distribution 6.x-1.16.

How do you restrict SE spiders to crawl user pages when the url alias is structured like so mysite.com/username? If I disallow the user system's url mysite.com/user/ will it subsequently disallow the alias as well?

I note that the bulk of the spam comments posted on my site come from the same few accounts. I block them when I notice, but by that time they have already flooded my site and even with the anti-spam module takes a lot of time to delete all their comments. What I'd really like is the ability to prevent users from having more than two unapproved comments. Is there any module or simple change that allows me to do this?

Alternatively I'm thinking of using Disqus, specifically for their blacklist ability. Does anyone have experience with that?

• Advisory ID: DRUPAL-SA-CONTRIB-2013-051
• Project: Services (third-party module)
• Version: 6.x, 7.x
• Date: 2013-June-05
• Security risk: Moderately critical
• Exploitable from: Remote
• Vulnerability: Cross Site Request Forgery