Active
Project:
LevelTen Apps
Version:
7.x-1.0-rc2
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Mar 2012 at 02:00 UTC
Updated:
20 Sep 2012 at 12:29 UTC
Aftet the upload and Install Updates steps I get an Access Denied error at this url
http://myserver.org/admin/apps/levelten/app/seotools/enable
This is a levelten application not sure if I should report this there?
I am using an admin account, have plenty of access rights.
Any help?
Comments
Comment #1
jec006 commentedApps uses the menu access hooks to control what appears at an stage of the process. Often when this sort of thing occurs its because an app doesn't list all of its dependencies and so can't be enabled even after its downloaded.
It would be good to report this on the levelten issue queue and see if they have any further information.
Hope that helps
Comment #2
febbraro commentedMoving to LTA to see if they have a line on what is going wrong.
Comment #3
gandhiano commentedsame issue. Tried multiple applications, part of OpenEnterprise installation profile:
* enterprise_rotator
* enterprise_portfolio
* seo
* enterprise_images
And then gave up. So, basically all applications related to OpenEnterprise (LTA) fail to install.
Comment #4
redheadedstepchild commentedSame thing here.
I installed wamp as a dummy server to play around and see if I could get a decent photography site up and running.
Fresh install of Drupal 7 Open Enterprise.
Can't install portfolio or careers and possibly a couple others. Those are the most important to me though because a portfolio is necessary for a photography site and careers can be used to list upcoming shoots and such if I need models, make up artists etc.
Anyone manage to get these to work?
I did try using an earlier version of the levelten apps module and same result.
Comment #5
jobcespedes commentedSame here when trying to install several apps, including rotator banner: access denied...admin/apps/levelten/app/enterprise_rotator/enable
Comment #6
mcctnt2000 commentedsame here
bump
Comment #7
mcctnt2000 commentedI think the priority should be changed to critical as the entire system is unusable until the issue is resolved.
Comment #8
mlapl1 commentedPlease do something fast as I for one will certainly give up on this. Sorry...
Andrew
Comment #9
junkbox commentedI have to agree, pretty much makes the entire profile moot. Bummer too, I was looking forward to rolling this out.
It should be noted that the apps fail to install at clean install time too. I didn't think anything of it as I knew I could probably install from the apps menu, but run into the same error as OP
However _blog installs fine. I get this on _carrers and _fAQs (thats as far as I've cared to go)
Comment #10
junkbox commentedCan't you just make these available as separate downloads? If the app installer is going to fail at least provide an alternative to the clunky FTP method.
Comment #11
kbell commentedHas anyone gotten any response or movement on this issue? I'm about to abandon ship, as the whole point of using a distro is so it can be *faster* than assembling it all by yourself...
+1
Comment #12
Road Runner commentedCan't use the apps installer because of ftp nonsense. When I try to do it manually these guys never bother to list the dependences and in one case I can't even find the module that the module installer reports against when I manually uploaded enterprise location. Real professional work here and great communications.
Comment #13
tresero commentedThis plugin sucks.
Comment #14
spyckedelic commentedI am encountering the same issue with the FTP settings. I can not use the apps, because the installation process fails because of the FTP problem. Help!
Comment #15
contraverse commentedFor the App-creators: I faced this error with Google Analytics and Google Analytics Reports. In my case error uccured in the manifest.app, dependencies and downloadables: if I specify Google modules here, I;ve got an error during enabling.
I fixed it like this:
1) creating feature "Depend", where all dependencies are written;
2) creating feature "Start" with the "Depend" module dependened;
3) placing all dependencies (UN-archieved) into the folder of "Start"-feature;
4) making Start.tar, or Start.tar.gz ... and so on.
5) when writing the manifest.app you don't need (or even must not) specify dependencies and downloadables.
Then it works. At last. :-)