tpr

When I upload an image that has an EXIF orientation data, it displays rotated in the admin (that is, it seems to have the right orientation). However when I echo it on the page (frontend) the item display non-rotated, that is the EXIF orientation is not applied. First I thought that I just crop it a bit and it will show up fine, but unfortunately after the crop a portrait image is turned into a landscape image, cutting off most of its area. I could remove the EXIF and rotate the images into the right position before the upload but unfortunately it's the client who does the upload. Is there something I could do, or is this a bug? Btw, is there a way to rotate an image in the admin?

Starting from around 3.035+ I can't replace images by drag-and-drop on an existing image. However, it seem to work if the field is set to hold only 1 image ("Maximum items allowed"). Can someone confirm?

v077 is up with some minor updates to InputfieldURLChecker, pageListIDs, FieldEditLinks and Hotkeys. The latter is the smallest but I like it the most because it fixes the malfunctioning ctrl+s in CKEditor after editing the content in the Source dialog. This will probably fix all similar cases when the CKEditor content is replaced (eg. by a plugin).

Most probably Tracy Debugger to disable modules.

I don't see the widespread usage of such a feature. I've made a similar text expander (part of a windows application) and used for like 2-3 times altogether

Nice and clean! Thanks for the insights. I've used a same approach on my very first PW site with the difference that I saved the json on saving the page (and it was for filenames for a JS slider with many images).

Have you copied autosize.min.js to the "site" folder?

My best guess is that you try I on a CKEditor field and not on a simple textarea. In this case you need the Auto Grow plugin (see above). If not, do you have any js error in the browser console?

Try adding a full absolute path instead of a relative one.

Yes, it was made using PW3. netcarver's module should work fine too, or you can use AdminOnSteroids in which there are some improvements too.

v075 is up: grouped several AdminTweaks and RenoTweaks items into a new submodule "PageListTweaks" added new tweak "Show page IDs in pagelists" to PageListTweaks moved AdminOnSteroids.scss into the "src" subfolder

No, if it was in a subfolder PhpStorm would compile the CSS in that subfolder so it won't overwrite AdminOnSteroids.css in the module's root (which is used by the module). I could add it to .gitignore but I'm using/testing AOS in different PW installs and having the source file always at hand makes things easier. Anyways, I think your PhpStorm file watcher needs a better configuration- does it compile all scss files from the modules directory? If so, that doesn't sound too good to me. I'm using gulp and I always explicitly set what file or what subdirectories to watch.

How about this for page IDs in the page list? I wanted something that is always visible but still less obtrusive.

It's not absolutely necessary of course. Would it help if I put it in a subfolder?

Success! Try upgrading to version 021.

I could duplicate the issue, it happens if your Hanna code type is set to PHP. I will try to find a fix or a workaround.

It is interesting because this is the way I use it and no issues here. What is your Latte module version and the open-close tags for Hanna? Do you have other textformatters applied to body? I have Video Embed for Youtube/Vimeo and they work fine together.

Could you share your current code? I haven't used it in .latte files, only in CKEditor.

I have something like this in mind: [object_name separator selector separator property] eg. [pages::template=news,title*=rock::title] If its an array, use the first item. Wouldn't this be more flexible?

Here is the code I have used with Tracy Console to remove fields: $fieldgroup = wire('fieldgroups')->get('forms'); foreach(array('admin_column_left', 'admin_column_left_END', 'admin_column_right', 'admin_column_right_END') as $ff) { if(!$fieldgroup->get($ff)) continue; $fieldgroup->softRemove($ff); $fieldgroup->save(); wire('fields')->delete(wire('fields')->get($ff)); }

I've run into this several times and it seems like a bug, or at least it's misleading. Steps to reproduce: Add a new template, eg 'news' Set its fieldgroup to another template, eg. 'basic-page' Edit a field that is in 'basic-page' template, and remove from all templates Now you you would assume that you can delete the field because it's not used in any templates, but you can't. Trying to delete from api reveals that it's used by the 'news' template, which obviously shouldn't be true because it uses the fieldgroup of 'basic-page'. Unfortunately I can't set the 'news' template's fieldgroup to another one because of data loss. I could remove it only via api using fieldgroup->softRemove(). Is there a better way of getting rid of such fields?

Thanks @justb3a for the updates, it's getting better and better! There's a PHP notice in the new release: PHP Notice: Undefined index: otherField in .../site/modules/ImageExtra/ImageExtra.module:992 If you use Tracy Debugger it's easy to spot.

Speed (page load time). Currently it's about 3 seconds which was better when the site was non-https. If you ask me it's still fast enough but it's not about me

It's about a 10-page (mostly static) website so GC is in this case an overkill. But it would be nice to have a detailed tutorial of using PW with cloud.

Thanks. Seems like a lot of trouble for minimal benefits, at least from a dev POV (maintenance, updates, etc).