I tried to create an image ad and when clicking on select it gave me the error An HTTP error 403 occurred.
/node/add/ad/ahah now my upload module is broken and I cannot upload anything

Comments

jeremy’s picture

jeremy commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Are you still having this problem? I have never heard of this happening before, so we need to find out what's unique about your installation. Is this a new ad module installation, or an upgrade? What ad modules are you using? What OS is Drupal running on?

What contrib modules are enabled? If you disable them all except the ad modules, does the problem go away? Perhaps there's a conflict with another module's JavaScript?

vip_sa’s picture

vip_sa commented

Hi Jeremy

I am not having the same problem anymore. I deleted the site and redone it and now it's working and I haven't had any problems so far. Thanks for your response

jeremy’s picture

jeremy commented
Status: Postponed (maintainer needs more info) » Fixed

I'm glad it's working for you now. Closing issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Molot’s picture

Molot commented

Just for future reference: this message appears when server dies when you are transmitting data, like in ajax requests when site tries to load addidtional fields and simply can not. This is not an Drupal issue. If it happens to you, make sure that server is alive and stable and you actually can ajax load stuff, permissions are OK and so on.

wiremuse’s picture

wiremuse commented
Status: Closed (fixed) » Active

I am having this issue and have no idea why it's coming up.

fizk’s picture

fizk commented
Status: Active » Closed (works as designed)

Just ran into this issue. The solution is to go to /admin/user/permissions and grant permissions to the user trying to create an ad.

jerdiggity’s picture

jerdiggity commented

Honestly I don't think there's a problem anywhere with the coding or with permissions (well, not in my case, at least).

My case:

There are a lot of browser plugins and/or full executable programs that help try to block annoying ads one might encounter while on the internet. One in particular is called Privoxy, and sometimes it appears as though it does its job a little too well.

For instance, when my browser is configured to tunnel through the local proxy connection provided by Privoxy, if I then visit node/add/add on any of the sites I administer I'll receive the 403 error as stated above. At first I thought it had to be a bug with the code since it was happening everywhere, but then I noticed it was not happening when I'd make the same attempt at http://localhost (because by default, all proxied browser requests apply to every site except for localhost and 127.0.0.1.

So, just a heads up: if you use an ad-blocking program of any type, there's a chance that the error you're receiving is no more than the ad blocker simply doing its job. (And if you think about it, considering the nature of the Ad module, the whole thing is kind of ironic in and of itself.) ;)

j