ottogal

I understand. But then the hint under Instructions ("... or use the "Protect Entire Site" shortcut below") should be removed in this case, too.

On the Settings page of the module PageProtector 0.1.4 the "Protect Entire Site" shortcut is missing. Was it removed intentionally?

@adrian: Thank you for your time, anyway. At the moment I don't have the time to dig deeper into it, but surely will try later.

Thank you, adrian. Yes, I'm using the PageProtector module (forgot to mention it). Members get only page view, not page edit permission. They should not have access to the backend.* Members have the roles "members" and "guest" - you can't remove the guest role from a user. They don't have any of the roles with page edit permission. *Edit: This doesn't work - they have access to the pages tree (not wanted), but see just the view buttons.

I read all over the docs and the forum about protecting certain pages from access and wonder why my efforts are unsuccessful. The situation (simplified): Pages tree Home - Free Stuff - - Free1 - - Free2 - Private Stuff - - Private1 - - Private2 Free Stuff and its children have the template "standard"; Access managing is set to No. Private Stuff and its children have the template "private": in its Access settings the page view option is unticked for the guest role. Apart from superuser and guest there are the following roles: editor member The editor role grants page edit permission for all the pages. Users having the member role have to log in to get acces to the private pages. Now my question: What do I have to do to give the member users page view access exclusively for the private pages? (That is, they should not see the pages of template standard.) What I tried: In the Settings of the page Free Stuff I ticked Protect this page, then Protect children too. As Allowed roles I selected all but the role member. So I expected that a member user would no longer have access to the Full Stuff page nor its children. But that doesn't work. Maybe I'm missing something obvious. Any help is hihgly appreciated!

If I understand it right, using the options 'outer_tpl' => '<ul class="uk-nav uk-nav-parent-icon" data-uk-nav>||</ul>', 'inner_tpl' => '<ul class="uk-nav-sub">||</ul>', 'parent_class' => 'uk-parent', should do it.

Stumbled over this old thread... These are different: 1 kB = 1000 B vs. 1KB = 1024 B https://en.wikipedia.org/wiki/Kilobyte (In former times, some producers of harddisks, even if they indicated the capacity in KB, they meant kB - so it looked bigger...)

No, I haven't installed any other image related modules.

Applying your modified function on my test image I got this output: Searching the web for information on the Exif tag Orientation you find dozens of sites and forum posts which show the subject is really a complex one, given that various hardware and software is treating it differently. So asking for the camera model was not as far-fetched as it seemed... Here's one link I found quite instructive: http://www.impulseadventure.com/photo/exif-orientation.html Edit: Two more links: http://www.daveperrett.com/articles/2012/07/28/exif-orientation-handling-is-a-ghetto/ http://keyj.emphy.de/exif-orientation-rant/

@horst: Strange things are going on. As you proposed I set autoRotation to false in both the config settings imageSizerOptions and adminThumbOptions, and put your image call in a template, used by a newly created test page. Result: Already with the upload of the test-image to the images field of the test page the created thumbnail was autorotated (i.e. displayed upright). Viewing the page, the half-sized image is oriented correctly, too. Inserting the original, full sized image into the body field (textarea/CKEditor) resulted in an autorotated output (backend and frontend). In the folder /site/assets/8765/ (where 8765 is the id of the test page) there is the file image test_1.jpg (width 600), not rotated like the original, and the half-sized image test_1.300x0.jpg, rotated to the correct orientation. (*) To crosscheck I reset the autoRotation settings in the config both back to true. Now both the admin-thumbnail in the backend and the half-sized image in the frontend are displayed not rotated (the latter one, inserted by the template, of course doesn't show in the frontend). But the full sized image inserted via the CKEditor ist autorotated correctly, both in backend and frontend... Thanks a lot, Horst, for your help! (*) Another strangeness: The original file I uploaded was test_1_.jpg, i.e. the name had a trailing underscore. This obviously is removed by PW processing the image. (But I don't think that has any influence on the problem in discussion.) EDIT: I also called your function checkOrientation(), it returned nothing.

I encountered the issue after having imported a bunch of images from a folder in the file system. (They have been used before on a website made with Modx Evo, where it never happened.) These images have been shot by various cameras; the issue occurs f.e. with the Canon IXUS 750. But I don't understand why the camera model is of interest: The thumbnails created by ProcessWire are using the original image, containing the Exif data. Hence something is wrong with this thumbnail creation, isn't it? (Or I'm doing something stupid.)

But obviously the image resizer rotates just the large version, not the thumbnail. Shouldn't it do this too, before it discards the Exif info?

Thank you, Horst. But it seems that the auto-created admin-thumbnail doesn't receive the Exif information from the original image: Using IrfanView and its plugin METADATA.DLL, I open the thumbnail and look into Image>Information - I don't even see the button "Exif info" (which is there on the original image).

Uploading image files to the image field of a page, I get a problem if the original file has the Exif tag "Orientation" set to "Right top": The auto-created admin-thumbnail obviously doesn't get the Exif information. So while the image itself is auto-rotated to be displayed "upright" (in backend and frontend), the thumbnail is not. To get this "repaired", do I have to use an external image processing software to rotate these images manually?

Thanks @adrian, hadn't seen that. It's a smart solution - but not easily found...

Do I just miss something? On the Details tab of a field of type PageTableExtended you can Select a parent for items. But when done, you can't switch back to the option no parent is selected. Is there a way to do it?

Just a hint: Adrian's addition to admin.php (see post #35 in this thread) - while working well in PW 2.7.0 - is causing an error in PW 3.02: The class pageArray() is not found.

Ah, of course. You made my day, thank you!

Thanks for the fast reply! Deleting the page Admin>Setup>Batcher was successful after unlocking Admin>Setup for editing. But a new install is refused like before: Same error message...

Hi all! On a fresh installed PW 2.7 I added a few pages and subpages to the tree. I installed the Batcher module and used it to batch unpublish or publish pages selected by template=basic-page. No problems so far. But now I made a mistake. Having found that the pages I wanted to unpublish all had an ID greater than 1013, I tried the selector id>1013. Obviously some pages related to the Batcher module matched this selector and went unpublished too. The link to the Batcher module (that was in the menu Setup before) had disappeared, so I could not use it anymore. Now I tried to uninstall Batcher and reinstall it. I got this error message: So my questions are: Is this an incompatibility of the Batcher module with PW 2.7? And, more important: What can I do?

Thank you for this valuable hint!

Thank you both. I will try Beluga's menu.

Hi all, happy to have found ProcessWire a while ago - yet another MODX refugee - and glad to have discovered PocketGrid recently I now am looking for a simple responsive menu (pure CSS or CSS+jQuery) which nicely integrates with PocketGrid. (Something like the menu in Pure - but this depends on their own grid.) Any hints? To not forget: Kudos to Ryan and to the great community!

One tiny weakness: The subtitle Produkte . People . Prozesse gives the misleading impression to be a menu of three items - resulting in an irritating navigation experience...

Despite my fast internet connection the page needs more than 25 seconds to load. Some visitor might jump away before...