tpr

AdminOnSteroids

Recommended Posts

@Robin S Could you tell if there's a body class or something that I can use to disable the relative position for H1's on those sites? I don't have ProDevTools to check.

@Speed Could you elaborate a bit more? Also, what AOS version are you using? A few versions ago the search could be focused using double-tap the Shift key but that was removed because such issues you mentioned.

Share this post


Link to post
Share on other sites
8 hours ago, tpr said:

@Robin S Could you tell if there's a body class or something that I can use to disable the relative position for H1's on those sites? I don't have ProDevTools to check.

Nothing useful on the body I think but there is a class on the h1 and also its containing div:

2016-12-15_093642.png

  • Like 1

Share this post


Link to post
Share on other sites

v109 is up - see the readme file on date formattig:

  • PageListTweaks: ability to format unix timestamps in pagelists
  • PageListTweaks: using %field.property% will output the value in the user's language (if available)
  • PageListTweaks: always show extra actions
  • fixed language translator filterbox not appearing
  • possible fix for unclickable select dropdowns in ProDevTools API Explorer (reported by Robin S.)

"Always show extra actions" was a client request and removes the need to click on the ">" icon to see the extra actions. This can be handy for power users or when you often need to toggle pub/hidden states of pages. Or simply lazy :)

aos-alwaysshowextraactions.png

 

  • Like 4

Share this post


Link to post
Share on other sites
On 12/14/2016 at 6:03 AM, tpr said:

 

@Speed Could you elaborate a bit more? Also, what AOS version are you using? A few versions ago the search could be focused using double-tap the Shift key but that was removed because such issues you mentioned.

Usually, If you click on any input box in PW you'd see cursor blinking. This will confirm that input box is active. Now If you hold down Shift key on keyboard before you could hit on any keys on keyboard (i.e. to create first capital letter). The input box becomes deactive, the blinking cursor will disappear  The current version i had problem was 0.9.7.  I just updated to 1.0.9... Unfortunately, the problems still exist. 

Share this post


Link to post
Share on other sites
On 12/15/2016 at 10:43 AM, tpr said:

 

Is the search box activated? The feature I was referring was removed in v0.999 so perhaps it's only a cache issue on your side. Try hard reload and see if it helps.

 

Yes, clearing cache have solved issues... Now I am facing a new problem right after updating. This come from old tread discussion on page tree If you can remember...

With this code that saved in /site/template/admin.css...

.PageListItem:not(.PageListItemOpen) 
span.PageListNumChildren.detail:not(:empty):before {
    content: " ← click to show children - Number of Children: " !important;
}

This showed up without problem on localhost running latest update of AOS 1.0.9

localhost.JPG

after transferring files from localhost into livehost... It doesn't show, seem like admin.css isn't recognized.

livehost.JPG

It happen right after I updated AOS 1.0.9. However, I tried another approach. I've added site/template/admin.css into asset path it still wouldn't recognize. I have uninstall and reinstall, refresh cache and yet problem still exisit. 

 

Share this post


Link to post
Share on other sites

admin.css works fine here with the code above, in PW 3.042, AOS 1.0.9. I see you have "site/template" and not "site/templates", is that only a typo?

Can you check using the Network tab in the devtools that admin.css is not loaded? (using Chrome, you can filter by file types)

Share this post


Link to post
Share on other sites

Template with no "s" was my typo in this thread only.

Here's dev tool

filter.jpg

Seem like it did not admin.css when i filtered it out. Although file is already there in livehost site same way I did in localhost.

ftp.jpg

 

 

 

 

Share this post


Link to post
Share on other sites

hi tpr,

do you know where this glitch comes from?

how it should be (AOS off):

2016-12-18 15_08_54-Program Manager.png

how it is (simple process module just returning "hallo"). sticky header OFF:

2016-12-18 15_09_08-Program Manager.png2016-12-18 15_10_20-Program Manager.png

is this a bug or did i forget a setting? thank you for your help!

Share this post


Link to post
Share on other sites

Most likely H1 tag not being full width or it is inline-block.

Share this post


Link to post
Share on other sites

h1 is float: left; - i don't know why, it must have to be a setting of AOS. it's quite hard to find out what setting it could be so i thought you may have an idea?

Share this post


Link to post
Share on other sites

It's the "headBtnToTitle" as you can see in the dev tools, coming from "Place header button next to the main title" from RenoTweaks.

  • Like 1

Share this post


Link to post
Share on other sites

@Speed are you sure you can access admin.css directly in your browser? Plus AOS checks if the file exists, can you confirm that PHP can access it? (maybe a file permission issue?)

Share this post


Link to post
Share on other sites
5 hours ago, tpr said:

@Speed are you sure you can access admin.css directly in your browser? Plus AOS checks if the file exists, can you confirm that PHP can access it? (maybe a file permission issue?)

Edit: File permission for admin.css is set at 644 as default following config.php.  I have created new css file and call them two.css, added same code string, and set   site/templates/two.css into asset path. It doesn't detect two,css either. Can you elaborate how could I access admin.css through browser. Sure I can access .css for template with browser but not knowing how I could this for admin. 

Here are view source for Admin... it seem like it isn't detecting admin.css from site/templates/...

viewSource.JPG

Share this post


Link to post
Share on other sites

Thanks, just noticed you are running PW from a subfolder so most probably AOS is using relative paths and that's why the assets are not loaded. I will post a fix soon.

  • Like 1

Share this post


Link to post
Share on other sites

v112 is uploaded and contains the submenu feature for custom nav items. See the readme for the instructions.

On the default theme its appearance is similar to the other 3rd level menus:

aos-submenus.gif

  • Like 3

Share this post


Link to post
Share on other sites
On 12/20/2016 at 2:40 AM, tpr said:

 

@Speed

Could you try this? It's working for me when PW is in a subdir or in the root.

AdminOnSteroids.module

 

Module that work for you... was this working on localhost or livehost?  It didn't work on me when I download and tried yours from livehost but worked on localhost. Although I did some test, I've added the code string at the very bottom of AdminOnSteroids.css. and this worked on livehost. So I am guessing somewhere in your module, i didn't detect admin.css in subpage of livehost. 

Share this post


Link to post
Share on other sites

I tried it on two servers (livehost), in a subdir and in the root.

You could try to uncomment the series of bd() calls in line 913 and further down in 961 to see what paths/urls AOS tries to use (requires Tracy Debugger).

You can update the module from the directory as it contains these fixes.

Share this post


Link to post
Share on other sites

Hello @tpr

here is an idea, what can also be useful for admins: It would be great if there will be a drag and drop possibility in the forms to change the position of a field in the form itself. You have added a great function to edit a field directly from the form.  So changing the position of the field in the form directly would also be a great addon (but maybe difficult to implement?!?)

I hope you understand what I mean. At the moment you have to open the template directory and change the position of the fields there.

With roles permission you can make this only accessable for superusers. Its only an idea.

Best regards Jürgen

Share this post


Link to post
Share on other sites

I think this feature won't be that hard to implement but I see it as an edge-case so I'm not sure too many users would use it.

The UI would be another question, I think the current "Edit template" tooltip could have an extra icon (eg. "Edit fields order"), and clicking on it the fields could be drag-and-dropped. But again, I would like to see others voting for this feature.

Share this post


Link to post
Share on other sites

i don't understand what you mean jürgen... you can edit the field's position in the template editor. it's only 1 click away from the page-edit-screen.

Share this post


Link to post
Share on other sites

But it's not wysiwyg and he's getting lazy at the end if the year :)

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180528, v1.0.4 add custom select statement option 180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen