Jump to content
apeisa

Fredi - friendly frontend editing

Recommended Posts

@apeisa This module is fantastic!!  It makes editing so much easier.  Thank you.

I've been playing around with the various configuration options and have come across a problem, possibly because of the way my site is built.  I can get fredi working on pages that call in a header and footer but can't get it to work on my content blocks.  

For setup I have a page with header and footer that pulls in children as content blocks like so:

<?php foreach($page->children as $child) echo $child->render(); ?> 

I tried targeting the child pages using $pages->get in the template file but it doesn't seem to work.  I'm not sure if this is because the blocks have no header and footer or if it's because fredi can't find them.  

Is it possible to use fredi in this way or maybe to target the block template itself?

Share this post


Link to post
Share on other sites

@photoman I'm not sure if this is what you want, but here goes:

<?php

foreach($page->children as $child) {
    echo $fredi->render("all|the|fields|you|want", $child);
    echo $child->render();
}

?> 
  • Like 1

Share this post


Link to post
Share on other sites

Thanks diogo.  I tried your solution but I still can't get it to work.  When I add your code to the parent template file and view the result the page renders fine but there are no fredi links.  Here's the code I entered.

<?php
foreach($page->children as $child) {
    echo $fredi->render("body", $child);
    echo $child->render();
}
?> 

What I'd expect to happen is all the children that have a body field would be rendered with an edit link.  I tried various multiple field combinations but no joy.  I'm not quite sure why it's not working.  

For simplicity sake let's say one of the child templates was just this:


<div class="span4">
<?=$page->body?>
</div> 

What's the best way to work with fredi using the example above.  Does it need to be called from the parent page template or can it be initialised in the child template itself?

Share this post


Link to post
Share on other sites

$fredi should work from both, but it might be you need to load $fredi again ($fredi = $modules->get("Fredi")) in your child template.

<?php
$fredi = $modules->get("Fredi");
foreach($page->children as $child) {
    echo $fredi->render("body", $child);
    echo $child->render();
}

Code snippet above doesn't show edit links even for superuser? How about changing it to $fredi->body($child)?

  • Like 1

Share this post


Link to post
Share on other sites

Aha! That did it.  In the end I didn't need to write the code as above, all that's required is $fredi at the head of the child template like so:

<?php $fredi = $modules->get("Fredi");?>

Then just call as normal using 

$fredi->render("heading|body|etc");

Many thanks for your help apesia and for writing such a cool module  :)  

Share this post


Link to post
Share on other sites

@apesia I've been happily playing around with Fredi and have a small suggestion.  The echo $fredi->renderScript(); call is only required when the user is logged in but at the moment it's printed in the header regardless of whether the user is logged in or not.  

I know this won't have a massive impact on page load speed but it adds another 2 http requests which aren't really necessary.  Just a thought.

On a slightly different note I noticed that the admin field column widths are not reflected on the front end.  I'm not sure if this was on purpose to keep things responsive?

Here's what's missing:

class="InputfieldColumnWidth InputfieldColumnWidthFirst"   (These styles are in UI.css)

and also the inline style that defines the width in the backend eg "width:20%".    

Share this post


Link to post
Share on other sites

You can add some checking whether to load script & css yourself. I don't want to add that check there since that method is just a shortcut anyway.

There is some discussion about column widths earlier in this topic. In short: yes, they are intentionally left out just because ideally just few fields are used and original widths probably don't work in that case.

Oh, and thanks trying Fredi and thanks for your feedback! Highly appreciated.

Share this post


Link to post
Share on other sites

Thanks apeisa I didn't think of that.  For anyone else who's interested just add this to your header instead of the usual call.  Nice and simple. 

<?php $fredi = $modules->get("Fredi");
   if ($user->isLoggedin()) {
   echo $fredi->renderScript();
   };?>

Totally understand your reasons for making the column widths 100% as the original concept was about editing on a field by field basis.  My sites are built in blocks and I find myself grouping fields on a block by block basis as it's quicker for the client to edit and means I can output less edit links.  

It would be great to have the markup available to target with css even if it's not used in your default css file but either way I'm very happy.  So good to have fredi.

  • Like 1

Share this post


Link to post
Share on other sites

Just add ProcessFredi.css to your module folder and add any custom css you need.

Share this post


Link to post
Share on other sites

Hi apeisa.

Thank you for this plugin, works a treat. How hard do you think it would be to adapt CKEditors inline editing feature so we could literally just edit the page there and then and see exactly how the page would look in real time?

Regards,

Share this post


Link to post
Share on other sites

Thanks for the feedback madmax. I am not planning to take this into that direction. I think it would be better to have separate module for that.

Share this post


Link to post
Share on other sites

I found pretty rare bug from Fredi and I couldn't think of clear fix for it: https://github.com/apeisa/Fredi/issues/4

 

Page fields doesn't work, if custom php code used to find selectable pages

Problem seems to be with $page variable - it somehow doesn't respect it, it believes the $page is the modal Fredi Edit Process page instead of the context page.

How to replicate: edit page field and open "input" tab. Open "Custom PHP code to find selectable pages" and add something that uses $page. Like "return $page->parent->children;"


Now when you edit that field through Fredi you get totally different results than you would expect.

To be honest I don't have a clue why $page works when using normal ProcessPageEdit but not when using FrediProcess. Any help?

Share this post


Link to post
Share on other sites

Ah, I finally found it. This is why custom selector stuff fails on FrediProcess: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/Inputfield/InputfieldPage/InputfieldPage.module#L141

I think cleanest option would be if getSelectablePages() method would be hookable. Any hopes to get three underscores there Ryan?

  • Like 2

Share this post


Link to post
Share on other sites

I have new version coming that introduces ability to create new pages. I would be extremely happy to get some feedback about the methods and arguments I am planning. Currently it works like this:

$fredi->newPage("templatename", "title|summary|body");

or

$fredi->newPage("templatename", "title|summary|body", $parentPage);

That would open new modal with title, summary and body fields. By default it creates new pages under the current page, but you can define alternative parent page there also.

I have also created ability to set fieldWidths, just add =XX to fieldname and it gives the width. Those can be used both in edit and new page modals. Like this:

$fredi->render("title|author=50|summary=50")

I want to take this further: defining required fields and also for new pages prevalues and possible hidden fields. This means that simple string based fields definition doesn't fly that far, or it needs some super nice syntax. Ideas?

  • Like 6

Share this post


Link to post
Share on other sites

I have new version coming that introduces ability to create new pages.

Fantastic! Can't wait to try it out. Do you plan to release it to GitHub in the next days?

Share this post


Link to post
Share on other sites

Not sure about next few days, but in week or two at least. Want to test it more here.

But so far - it seems to provide super nice editing interface.

  • Like 2

Share this post


Link to post
Share on other sites

Hi apeisa,

Fredi is fantastic! Thanks for sharing this. I've been using it with Chrome. I can't seem to get it to display the form in Safari though...(v6.0.4 on OS X).  

The modal shows up, and expands to the right size, but no form shows up - just the spinner. The form is there in the source code (within the iframe), but it isn't displayed. Maybe it could it be the z-index or maybe a source-order issue with the modal?

Thanks again!

Edit: forgot to mention - no javascript errors appear in the console

Share this post


Link to post
Share on other sites

Try updating the chrome. It was a bug with chrome version 25 and below I believe.

Share this post


Link to post
Share on other sites

It's actually Safari I'm having trouble with - Chrome is fine.

Share this post


Link to post
Share on other sites

Ah, sorry I read your message in hurry. I guess it's a bug with earlier webkit then. I'll take a look at it.

Share this post


Link to post
Share on other sites

I've come across an error which is stopping fredi working with images in repeater fields.  I'm not quite sure why it's happening but this seems to be on all my templates with repeaters that contain image upload fields.

As an example I have a carousel as a repeater (code below).  If the carousel is filled with images from the backend it works perfectly.  When I try to fill it with images using fredi on the frontend the edit modal pops up as expected and the "choose file" button for the field brings up my file explorer.  When I choose an image you can see that the image is trying to load but nothing happens.  

The strange thing is this only happens with images.  I have other repeaters that contain both images and text and the text can be edited with fredi, just not the images.

Is this a bug or do you have any suggestions to fix the error?

Here's an example of my setup:

Call fredi at the top of the template:

<?php $fredi = $modules->get("Fredi");?> 

Example of an image repeater I'm using:

<?php 
    foreach($page->sliders as $k => $slider) {		
    $active = ($k == 0) ? " active" : "";		
    $image = $slider->image_single->size(660,220);
    echo  "<div class='item {$active}'>
    <img class='photo' src='{$image->url}' alt='{$image->description}' />
    </div>";
}?> 

Call the fredi edit link at the bottom of the template:

<?php echo $fredi->render("sliders");?> 

Share this post


Link to post
Share on other sites

It's a known issue of Fredi. Sorry.

Share this post


Link to post
Share on other sites

I think it is definitely fixable, although I have tried many things already. I might need Ryan's help there to find it out.

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   0 members

    No registered users viewing this page.

  • Similar Content

    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...