modxbot / migrate

A testground for migrating issues and other such fun
0 stars 0 forks source link

can't add usergroup to media source #7574

Open modxbot opened 12 years ago

modxbot commented 12 years ago

rdaneeel created Redmine issue ID 7574

i'm logged in as Administrator , with sudo acces. i'm trying to add a usergroup to a mediasource. selecting the usergroup goes well also choosing the role. BUT the dropdown for 'policy' doesn't show anything,

therefore i can't save thus can't add the usergroup to the media source.

Why can't i select a policy?

modxbot commented 12 years ago

rdaneeel submitted:

As it seems the dropdownlist for 'Policy' is empty in more places

XoD commented 12 years ago

xod submitted:

I don't know why this doesn't get more attention...seems like it's working for most of you guys...but I have this problem constantly ie I can't really use anything else than the standard Filesystem MediaSource and restrict access for it, which includes also myself as SuperUser to be restricted to only the directories the editors can see...

to show what the problem is, I made a short screencast, hope this gets fixed soon =)...

http://www.youtube.com/watch?v=1M84PUvtzk0

gadamiak commented 12 years ago

gadamiak submitted:

I confirm this on 2.2.5-dev (release-2.2 branch in GitHub). I can't observe this in 2.3-dev (develop branch).

modxbot commented 12 years ago

Eiventeleiron submitted:

Can't reproduce on 2.2.4...

gadamiak commented 12 years ago

gadamiak submitted:

I think I found the reason -- the MS policies are messed up. In my case it's a Git release-2.2 branch install.

There is more:

Quite weird!

modxbot commented 12 years ago

Eiventeleiron submitted:

Was it a clean install of MODX or after several updates?

gadamiak commented 12 years ago

gadamiak submitted:

It was a clean install from release-2.2 branch, commit 02fc8e9.

roele commented 12 years ago

roele submitted:

Also facing this issue. Request looks normal to me but does not return any results.

Request URL:http://www.myserver.com/connectors/security/access/policy.php Request Method:POST Status Code:200 OK Request Headersview source Accept:/ Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Connection:keep-alive Content-Length:122 Content-Type:application/x-www-form-urlencoded; charset=UTF-8 Cookie:modx_setup_language=en; PHPSESSID=f991ad85715bc5af8c529e6ae06822d1 Host:www.myserver.com modAuth:modx504c8561f34d44.72058927_150657cdfcde453.26018792 Origin:http://www.myserver.com Referer:http://www.myserver.com/manager/index.php?a=51&id=1 User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4 X-Requested-With:XMLHttpRequest Form Dataview URL encoded start:0 limit:20 action:getList group:MediaSource query: HTTP_MODAUTH:modx504c8561f34d44.72058927_150657cdfcde453.26018792 Response Headersview source Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection:close Content-Type:text/html Date:Fri, 28 Sep 2012 13:11:09 GMT Expires:Thu, 19 Nov 1981 08:52:00 GMT Pragma:no-cache Server:Apache Set-Cookie:PHPSESSID=f991ad85715bc5af8c529e6ae06822d1; path=/ Transfer-Encoding:chunked

X-Powered-By:PHP/5.2.9

Any known workarounds to get this work in the meantime?

gadamiak commented 12 years ago

gadamiak submitted:

After upgrade to latest release-2.2 the problem persisted.

I resolved it by manually editing database:

UPDATE `modx_access_policies` SET `template` = 5 WHERE `modx_access_policies`.`id` = 8;
UPDATE `modx_access_policies` SET `template` = 5 WHERE `modx_access_policies`.`id` = 9;
UPDATE `modx_access_policies` SET `template` = 6 WHERE `modx_access_policies`.`id` = 11;
DELETE FROM `modx_access_policy_templates` WHERE `modx_access_policy_templates`.`id` =7;
DELETE FROM `modx_access_policy_templates` WHERE `modx_access_policy_templates`.`id` =8;

Now I can assign permissions to media sources.

opengeek commented 11 years ago

opengeek submitted:

I'm still unable to figure this out or reproduce it. It seems to be an anomaly, perhaps caused by specific upgrades when specific data existed in the database. I have modified the resolvers not to resolve non-core Policy Template Groups when upgrading data for Policy Templates, and likewise for Policy Templates when upgrading data for Policies; they were previously setting any that did not match the core mappings to the Admin Policy Template Group and AdministratorTemplate Policy Template respectively by default. But I do not think that is related to the problem.

Since the confirmed reproduction is based on a release-2.2 branch git build, are you sure the core transport was built and a setup upgrade executed if you were upgrading an existing installation? Any other information or related errors from install logs (see core/cache/logs/install*.log) or other error logs when setup was executed?

Rx2 commented 11 years ago

rx2 submitted:

This is happening to us on a MODX Cloud install of 2.2.6 as well (upgraded from 2.2.5). Usually we briefly see the drop down show us something for a millisecond and then it disappears. Subsequent attempts show nothing until we logout of the manager and log back in. They, again, on the first attempt, we see something flash for a second and then it disappears. Tried in IE 9/10, Firefox and Chrome (latest versions).

Unfortunately we did not try it under 2.2.5 as we hadn't yet gotten around to making restricted users.

Nothing comes up in the Error log.

I did what was mentioned in the other thread (http://forums.modx.com/thread/77606/media-source-user-group-policy-missing?page=3#dis-post-446412), namely reinstalling 2.2.6 on MODX Cloud and now I can select an Access Policy for the Media Source.

wuuti commented 11 years ago

inreti submitted:

Can confirm for a clean 2.2.6-pl traditional installation. No update, just installation from tarball and normal configuration.

modxbot commented 11 years ago

funky_duke submitted:

In 2.2.7. I have the same issue. The Media Source Admin is empty and is linked to Media Source Admin Template. I have changed this manually to MediaSourceTemplate (by creating a new). Is this a bug in 2.2.7. ?

modxbot commented 11 years ago

paul_kemp submitted:

Same issue here with an upgraded 2.2.6 installation to 2.2.7. I have several installations but only one installation is affected...

modxbot commented 11 years ago

alezRu submitted:

Same trouble. I have version 2.2.7 upgraded from 2.2.6.

maxjo commented 11 years ago

maxjo submitted:

Same issue here. Fresh install MODX Revolution 2.2.7-pl (traditional). No errors in error-log.

elebrun commented 11 years ago

elebrun@bryant.edu submitted:

Same issue upgrading from 2.2.0-pl2 (advanced) to Revolution 2.2.8-pl (traditional). This was only a problem with our Media Source policies which were the only policies that shared a template. The upgrade created two new empty templates under the Admin group and attached those to the policies which lost all their permissions. This was fixed by updating the templates in the DB.

modxbot commented 11 years ago

clareoconsulting submitted:

Greetings.

This issue just appeared for me after an upgrade from 2.2.5-advanced -> 2.2.8. Re-running setup (without uploading any new files) fixed the problem.

Install log from the 2.2.5 upgrade to 2.2.8 did have what I suspect are related errors:

[2013-08-20 10:16:57] (ERROR @ /setup/index.php) Error 42S22 executing statement: 
Array
(
    [0] => 42S22
    [1] => 1054
    [2] => Unknown column 'modAccessPermission.policy' in 'where clause'
)
[2013-08-20 10:16:57] (ERROR @ /setup/index.php) Error 42S22 executing statement: 
Array
(
    [0] => 42S22
    [1] => 1054
    [2] => Unknown column 'modAccessPermission.policy' in 'where clause'
)

Forum thread that seems to be related (including more detail on my specifics) is here: http://forums.modx.com/thread/77606/media-source-user-group-policy-missing?page=4#dis-post-475445