Jump to content

Recommended Posts

Thanks for these updates. We'd talked about getting AdminBar bundled into the core distribution and I still want to do that. If you still want to lets try and get it in before 2.2. I just need to update the Modules system to deal with duplicates in case someone upgrades a system that already has /site/modules/AdminBar/ installed.

Share this post


Link to post
Share on other sites

No worries about that Ryan. I think it might be good idea to wait a little before trying to put this into core distribution. I want to make this easily extendable so that other developers can add their own "bells and whistles" into Adminbar or maybe even release modules that support / use AdminBar. It is pretty easy already, but will test this more and with good time.

Also committed few updates:

  • Possibility to customize look and feel (=css) by adding AdminBarCustom.css to module folder.
  • added logout link and removed gear icon from admin button
  • If you delete page, it redirects to the parent page of removed page and shows better notification "My Poor Page moved to the trash"
  • Instead of always showing "Add page" it shows "New press-release" if press-release is only allowed child template. (changed "add" to "new" because pagelist uses that term. So it is "New page" or "New templatename"

Share this post


Link to post
Share on other sites

Sounds great apeisa, will just go and test new version!  8)

Share this post


Link to post
Share on other sites

I tested this, and looks good. BUT I can't see the bar when I log in as a custom user, although I see the edit button I can't see the admin bar. Not guud ;D

Share this post


Link to post
Share on other sites

You see the edit button? Custom edit button from your template or adminbar edit button?

Custom user roles do need AdminBar permission to see and use adminbar. If you don't see that permission, please unistall & install adminbar.

Share this post


Link to post
Share on other sites

I only see edit link from template... Ah I see.

But I can't uninstall admin bar: Unable to delete pages of type '' !

Share this post


Link to post
Share on other sites

I can't deinstall the module, how can I fix that?

Notice: Trying to get property of non-object in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/PagesType.php on line 71

Notice: Trying to get property of non-object in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/PagesType.php on line 146

TemplateFile: Unable to delete pages of type ''
#0 [internal function]: PagesType->___delete(Object(NullPage))
#1 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#2 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('delete', Array)
#3 [internal function]: Wire->__call('delete', Array)
#4 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/AdminBar/AdminBar.module(318): Permissions->delete(Object(NullPage))
#5 [internal function]: AdminBar->___uninstall()
#6 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#7 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('uninstall', Array)
#8 [internal function]: Wire->__call('uninstall', Array)
#9 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Modules.php(455): AdminBar->uninstall()
#10 [internal function]: Modules->___uninstall('AdminBar')
#11 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#12 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('uninstall', Array)
#13 [internal function]: Wire->__call('uninstall', Array)
#14 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/modules/Process/ProcessModule/ProcessModule.module(241): Modules->uninstall('AdminBar')
#15 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/modules/Process/ProcessModule/ProcessModule.module(184): ProcessModule->renderEdit('AdminBar', Array)
#16 [internal function]: ProcessModule->___executeEdit()
#17 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#18 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('executeEdit', Array)
#19 [internal function]: Wire->__call('executeEdit', Array)
#20 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/ProcessController.php(194): ProcessModule->executeEdit()
#21 [internal function]: ProcessController->___execute()
#22 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#23 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('execute', Array)
#24 [internal function]: Wire->__call('execute', Array)
#25 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/admin.php(45): ProcessController->execute()
#26 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/templates-admin/controller.php(13): require('/Applications/X...')
#27 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/templates/admin.php(13): require('/Applications/X...')
#28 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/TemplateFile.php(88): require('/Applications/X...')
#29 [internal function]: TemplateFile->___render()
#30 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#31 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('render', Array)
#32 [internal function]: Wire->__call('render', Array)
#33 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/modules/PageRender.module(194): TemplateFile->render()
#34 [internal function]: PageRender->___renderPage(Object(HookEvent))
#35 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#36 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('renderPage', Array)
#37 [internal function]: Wire->__call('renderPage', Array)
#38 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(289): PageRender->renderPage(Object(HookEvent))
#39 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('render', Array)
#40 [internal function]: Wire->__call('render', Array)
#41 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/modules/Process/ProcessPageView.module(73): Page->render()
#42 [internal function]: ProcessPageView->___execute()
#43 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(267): call_user_func_array(Array, Array)
#44 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/wire/core/Wire.php(229): Wire->runHooks('execute', Array)
#45 [internal function]: Wire->__call('execute', Array)
#46 /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/index.php(181): ProcessPageView->execute()
#47 {main}

Share this post


Link to post
Share on other sites

Ah, it seems that my uninstall function is not backwards compatible :) Just a moment.

Share this post


Link to post
Share on other sites

Good to know, thanks Soma.

For everyone else who might download the AdminBarNew: if you want others than superuser to see AdminBar, then you need to a) uninstall + install Adminbar or b) add new permission "adminbar" and give it those roles that you want to see adminbar. Installing adminbar does add that role automatically for you.

There is one annoying issue left in IE: it throws "Load jQuery first" alert when you have tinyMCE fields in your template and you close the edit view (using slide/modal). Working on this...

Share this post


Link to post
Share on other sites

Just updated branches that master is now for 2.1 and AB20 is for 2.0. AdminBarNew is no longer.

So if you cloned this from github, you probably want to do something like this:

git checkout master
git pull origin master

(or just remove whole folder and clone it again)

If you have downloaded and unzipped, then just download again, but now from master branch.

Share this post


Link to post
Share on other sites

AdminBar is great! But you already knew that. :) Thanks for the update.

Share this post


Link to post
Share on other sites

Added multilang support for AdminBar. Also uses template labels if available "New Blog post" instead of just "New" or old db-style "New blog-post".

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Andrew - definitely looks neat. Although not sure how good fit that is for "inline editor", since that requires textareas - where Mercury and Aloha do work with any element.

Not sure when and what I will develop for Adminbar next. So far it has served our client needs pretty well.

Share this post


Link to post
Share on other sites

Does AdminBar support editing of pages different than currently visible in the browser? In other words.. If the visible page exist elsewhere in the PW but it is included and rendered based on a one or more segments.. is it possible to pass the real page->id to the AdminBar for editing instead of the page->id of the page with segments? Of course.. it will be great if after Save it returns to the initially displayed page with segments. :) Is it possible and/or easy to implement?

Thanks!

Share this post


Link to post
Share on other sites

I think that could be a good addition. There need's to be someway to tell AdminBar, that "editablePage" is different from "currentPage". Can you tell me more about the context you have this request? Using urlSegments probably?

Share this post


Link to post
Share on other sites

I mean urlSegments, sorry.

You understood me correctly. I was thinking if we could use a two session variables like "editablePage" and "redirectAfterSave" and to check if they exists before opening the AdminBar and after page save. I am not sure about any other way except session variables, probably you will have a better idea?

About the example context....

Lets assume we are storing our products pages in Home >> Products as children.

Also... we have categories stored in Home >> Categories and each Product page has a few Categories attached.

If we are browsing the www.example.com/categories/category_name/product_name/ we will see the product details page but actually if we open AdminBar we will edit www.example.com/categories/category_name/ if "/product_name/" is urlSegment1.

I am not sure if it is the best example, it is not the real one, but I am sure you understood me correctly.

What do you think? Should we use session variables or there is another way to pass php variables internally?

Share this post


Link to post
Share on other sites

I got it. Probably we can just add them as values for $page object, like this:

$page->abEditablePage = $pages->get($product_id);

$page->abRedirectPage = $page; // Not sure if this is ever required, we want always return to same url we were before editin?g

I'll hope to take a look with this sooner or later. Of course if you (or anyone else) likes to try hacking this you are more than welcome!

Share this post


Link to post
Share on other sites

Can't reproduce, works fine here in Chrome and Safari.

Share this post


Link to post
Share on other sites

Me neither. Tested on Safari, Firefox and Chrome on Mac.

Share this post


Link to post
Share on other sites

No problem here with the scrolling on Mac with Chrome.

I recently discovered a different issue, however. On a couple of my sites I am using SSL (https) for some pages, or for all of the admin pages. I find that if there is a mismatch where the live page is regular http and the admin page is https (or the reverse of this also, I think), then clicking "edit" on the adminbar will result in an "Unknown Page" error.

It was just recently that I was able to narrow this issue down to only sites that use SSL. Hopefully this can be fixed!

Share this post


Link to post
Share on other sites

Hmm... not sure how to fix that. How have you setup your ssl? Or I mean where you define that admin is always SSL and public is not?

We have always setup so that logged in users are https, so it will load just fine.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




×
×
  • Create New...