By lionheart8 on

Hi,
I have noticed since yesterday that any configuration, like selecting the weight is not working. Creating one is not a problem, but when I try to configure one, in Firefox, it leads to a blank page and in IE to a 403 error page, witha ridiculous message that I dont have permission to access the page or folder concerned!
I have no idea what could have triggered this - I must say I'd not done anything to do with blocks for a while.

I am logged in as admin!

What do I do to get it back to function?

Thanks

⋅ Categories: Drupal 5.x

Comments

lionheart8’s picture

lionheart8 commented

Surely, there must be someone who has had this or who might simply know what could be done ...

jefftrnr’s picture

jefftrnr commented

look at [domain]/admin/user/access to see if you've given access to admin

lionheart8’s picture

lionheart8 commented

Hi

Thanks for responding.
Actually its a long time since I wrote this & have been forced to do the site from scratch a few times.
I thought normally the admin comes by default with all access rights ...
In any case, in my case I think the combination of modules or their number or some other factor sometime into the building of the site causes the problem as before that, everything functions normally.

Currently, after checking the sequence of setting up some things, I came much further than before witout the problem coming up, but it turned up, affecting saving additional blocks after creating them or wanting to change the layout + editing access rights.
The logs show no errors.
After carrying out any of those functions & I save, no confirmation of the implementation is made & everything remains as it was.

A trick I used in trying to locate where the problem was was to temporarily transfer the complete site (currently on a private free server) to paid server with a site I look after, I assume with no (similar debilitating) limitations and everything functioned normally! That made me suspect something wrong on the current hosting server. May be some memory or other limitations? (There according to phpinfo it's 128m, though).
If the problem was memory related though, I used the measures recommended in support forums, etc & raised the memory settings in settings.php in steps from around 25M to over 100M, but it does not seem to help.

Anyway, a temporary solution was to make changes to the lay out + permissions here, saved them & then transferred the db tables concerned (block.sql, block_access & box.sql) replacing those on my current server.

I assume or hope when I transfer to a paid server, this wont happen again. If it does turn up ... I'm in deep trouble ...

[I must add that with Drupal 4.7.3 & 5.1 I had many more modules than at present, on the same server but never had any similar problem.]