After selecting images and gallery at admin/content/image_import, it gives me 'Acces denied, You are not authorized to access this page' error. Everything works perfectly with older version. Any idea? Thanks.

Comments

joachim’s picture

joachim commented

What is the path you are at when you get that message?
And which user are you logged in as?
I've just run this as uid 1 and it's fine for me.
It may be that batches can only be run by uid 1?

milosnemec.cz’s picture

milosnemec.cz commented

The path is (for example) www.domain.com/batch?op=start&id=54. I'm getting Access denied message after submiting Import button at admin/content/image_import page. I'm logged as uid 1.

joachim’s picture

joachim commented

What about other batch operations?

milosnemec.cz’s picture

milosnemec.cz commented

Hello joachim, thanks for the tip. Other batch operations work, but I found why image import batch failed. UPDATE statement in function batch_process() in includes/form.inc fails with "Got a packet bigger than max_allowed_packet bytes" warning. It's because mysql settings max_allowed_packet = 1M (my hosting plan) and serialized batch string exceed 1MB. So batch column is empty and this leads (function _batch_page() and function system_batch_page() in include/batch.inc) to Access denied page. Funny thing is that inserting error into watchdog table fails for the same reason (description contains statement exceeding 1MB). Well, it's probably Drupal Core issue. I don't know what to do now, because I can't tweak my mysql configuration.

joachim’s picture

joachim commented

I don't know much about batch API, but yes, sounds like core.
You can either move this issue there, or file a new one and point to this one.

milosnemec.cz’s picture

milosnemec.cz commented
Status: Active » Closed (fixed)

Drupal issue queue http://drupal.org/node/434032
Thank's a lot, joachim.

webengr’s picture

webengr commented

using image beta3
I found this problem also...

YES it should work with the default, 1M
and yes I tried only importing one tiny file, and it still failed....
someting in the recent beta's is different?
oh well

So ... I edited my /etc/my.cnf and restarted,
Since it was my server and it had plenty of resources, I set it
max_allowed_packet = 16M

reference also:
http://drupal.org/node/360463
and
http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html

evronique’s picture

evronique commented

I had the same problem as describe higher... I tried all the solutions except the patches ... the max_allowed packet, the memory_limit were good... and I just find the solution for me.
When I connect my database I put "localhost" to use the locale socket of the server. Normally it would work fine, but I don't know why, that will create all the problems describe. So we put the real address of the database and it works...
Hope that will be usefull for you !

asb’s picture

asb commented
Version: 6.x-1.0-alpha6 » 6.x-1.0-beta3

Hi,

same issue here with a fresh install of D6 and 'image.module' 6.x-1.0-beta3.

In my case, the problem was solved by raising the allowed file sizes at ./admin/settings/uploads. Those are limited through php.ini, but I belive they can be overridden in Drupal's settings.php. However, even changing the default "1 MB" to "2 MB" solved this issue.

Some kind of more meaningful error message than "access denied" and "an error occurred" would be nice ;)

Greetings, -asb

joachim’s picture

joachim commented

As far as I know this is to do with core.
If there is anything image can do, please reopen -- otherwise, comment on the core issue linked above.

Edit: oh, and add something about how to fix this to the image module troubleshooting docs page. Anyone can do that :)