This could be a problem with my specific setup but if it is I cannot figure out why so I wanted to see if it could be recreated and is indeed a legitimate bug. I am using the Events extension and am having a problem with it not recognizing user permissions correctly. I went in and added a column "group" to the events table so that each event could be assigned to a group. I also have a second table "event_groups" that has a FK relationship to the associated events column and also holds the title for each group. My GBP setup is "Main Table" is "btx_events_events" with the "Main Field" of "group". For the "Other Table" I have it set to my "event_groups" table with the "Title Field" being "group_name". This creates the user permissions setup that I desire, where I can assign a particular user as a publisher/editor for x number of unique groups. Then, when they are adding/editing an event, they only see events within the group(s) they have been assigned to and only those groups appear in the field dropdown when creating a new one. Where the problem occurs is even when all the groups they are assigned to are set at the "Publisher" level, the permissions still come back as only editor which only displays the "Save" button and not "Save & Publish". I looked into it a little bit and my $bigtree["access_level"] is actually returning blank because (I assume) in the getAccessLevel function there is no entry in the user's permissions ($admin->Permissions) under the key for my module. However, there is a key of my module's id under "module_gbp" and the sub-array does contain all the correct information (keys representing event group ids and values of "p") but the function never gets that far and instead returns the empty/null string found from $permissions["module"][$id];. I do understand that I don't have a permissions entry for "modules" because I have it checked as "No Access" at the top level (so for the whole "Events" module). But I don't want to set that as either "Publisher" or "Editor" because that would open up all the groups to my users and basically ignore/override my GBP.

After having thought about it, I'm not sure what the expected behavior would be if, for example, I marked a user as "Editor" for x groups and "Publisher" for y groups. I haven't spent any time looking at the processing to understand how it would behave if a user were to click a "Save & Publish" button for a record that they were technically only an editor of.

Hopefully this all makes sense. I realize I might be trying to do something that was not originally intended and if that's the case, any help/thoughts on how to try and accomplish what I'm after would be greatly appreciated.

I'm running 4.2.7 and I think I've found an issue with minimum images sizes not being applied if you're using a defined preset. There's nothing getting defined for $field["options"]["min_width"] or $field["options"]["min_height"] so it's always getting set to 0. If you set the values in the field type options directly then it is getting added correctly.

I'm trying to setup a routed template but the design requires an alternative header/footer than our standard ones. However, routed templates seem to pull in the _header.php and _footer.php files even if my routed/default.php file is completely blank. Is there anyway I can set it to not automatically pull in those files? Is my only choice to modify my router.php file?

Thanks

I'm having an issue (using 4.2.1 clean install) upgrading to 4.2.2 and it is also affecting trying to upgrade extensions (specifically the one most recently published for Form Builder) and I can't quite figure out what it causing it.

I believe I have narrowed down the bug to something happening in the installLocal (BigTreeUpdater) function. As part of debugging, I've been having the function die right after the call to backupDatabase to make sure everything is getting moved correctly but my core files never get moved to the backups folder. The backups folder and the core-4.2.1 folder are both created and the backup.sql file is stored inside them where it's supposed to be. However on the screen I'm getting a warning for the rename function that moves the old core into the same folder saying "access is denied (code 5)". So I figured something was wrong with either the permissions of the backups (sub)folder when it was being created but the sql file is created in there with no issues so it clearly has read/write permissions for that. Then I thought the permissions might be messed up with the core folder so I duplicated the backupDatabase call to put a second copy of backup.sql in the main core folder and it did that fine as well.

Now if I let the installLocal run all the way through without me killing it, BigTree acts like the upgrade was successful except the message returned says that I upgraded to 4.2.1 (which I'm already on). When I look at the core files and compare them with what  I know are updated files from 4.2.2 they don't match so nothing is getting updated. Another weird part is that in the cache/update/core folder the files that were extracted from the update.zip are no longer there but the entire folder structure for the core folder is. Now if I kill the installLocal function before it runs the rename that moves the new core from cache/update/core to core/ then all the files are there extracted properly.

So I'm stuck wondering why it looks like there is a permissions problem but I'm able to create files in all these folders but not move them? The same rename problem looks like it also plaguing extension upgrades when they're both called. Any ideas you have on what problem I might be experiencing would be most appreciated!

I created a module form where I have a matrix using a list display directly above a matrix that uses a callout display. There seems to be a problem if matrices appear in that order. The "callouts_no_margin" class gets added to the last matrix and adds a negative margin to it that pushes it up into the matrix above it. I believe the problem is on core/admin/form-field-types/draw/matrix.php line 5: $field["type"] = "callouts"; // Pretend to be callouts to work back-to-back

If I comment that whole line out, the fields display correctly, but based on the comment on that line I wasn't sure if there would be other unknown consequences of me doing that for different form field setups. So I wanted see if you knew if removing that line would negatively impact anything?

Thanks