Jump to content
apeisa

Fredi - friendly frontend editing

Recommended Posts

Wohoo apeisa hws a new baby! Great to have this!

  • Like 1

Share this post


Link to post
Share on other sites

Hahaa, thanks Soma :) It has little bugs with images/files and haven't even tested it with repeater yet, but other than that it seems to work nicely! This was superfun to code and actually took very little time and code so far.

Share this post


Link to post
Share on other sites

Let pw do its work and youll be fine. :)

Just have to remember to echo it!

Btw what about permissions?

Share this post


Link to post
Share on other sites

Alright! I can't wait to try this Antti. Quick question: will it let me work with your Thumbnails module too?

Share this post


Link to post
Share on other sites

Permissions should be fine. I check them on field level.

Marty: feel free to try. I think it might work with thumbnails already. If not, it shouldn't be a big tweak.

  • Like 1

Share this post


Link to post
Share on other sites
Btw what about permissions?

Oh, I had nice bug that showed edit links for everyone (and then login screen if user didn't have editing rights). Fixed now, show edit links are shown only for editors.

Share this post


Link to post
Share on other sites

Ok, just pushed nice little update. It should support pretty much all inputfields now (uses their native input processing). Only thing where I am having problems is ajaxfiles inside repeater (gives me response text: "page not saved (no changes)" after upload has been done). Repeaters without images works just fine.

It should be pretty trivial to build some kind of JS-switch to "show / hide" edit buttons. There is also $fredi->enabled = false that you can set if you want to disable edit links for some reason.

  • Like 1

Share this post


Link to post
Share on other sites

Uh nice,

a lot of little cupcakes inside your code to pick and learn from.

  • Like 1

Share this post


Link to post
Share on other sites

Apeisa i think you have to set some track changes when modifiying repeaters. Am on mobile so cant look.

Share this post


Link to post
Share on other sites

Thanks soma. That is what I have tried, not lucky yet.

Share this post


Link to post
Share on other sites

Does it works with language fields? Because all I get is a "edit" text instead of the body and a edit link.

Share this post


Link to post
Share on other sites

Haven't tested yet. Does it work with others? You have loaded js?

Share this post


Link to post
Share on other sites

Yes I have scripts. I get the link only with no text and if I click it just loads the homepage in the modal.

<span onclick="TINY.box.show({iframe:'http://pwmultilang.ch?id=1001&fields=body&modal=1',boxid:'frediModal',width:750,height:450,fixed:true,maskid:'bluemask',maskopacity:40})" class="fredi fredi-body">edit</span>

Share this post


Link to post
Share on other sites

I also just tested with a non language field and same issue as above. I don't know what is wrong.

Share this post


Link to post
Share on other sites

The url seems to be wrong. Do you have the process module installed? Does this selector work for you: wire('pages')->get("template=admin, name=fredi-field-edit");

Share this post


Link to post
Share on other sites

I just tried on a non language install, and got same issue.

Thanks, yeah it seems the process module doesn't get installed at all. Although it says it installs it, it doesn't.



I installed the proces module and now the edit link works and opens field, but the text still isn't shown/rendered on page...

Share this post


Link to post
Share on other sites

Multilang fields: it has few issues. It shows all languages right, but saves the "default" into "active" language. So if you are currently browsing with default lang, it discards all the changes for alternative languages. If you are browsing in alternative language, it saves default value into it.

Share this post


Link to post
Share on other sites

I'm on a other install with no languages. Still doesn't output the body text when using echo $fredi->body. Just the edit link.

Share this post


Link to post
Share on other sites

I just tried on a non language install, and got same issue.

Thanks, yeah it seems the process module doesn't get installed at all. Although it says it installs it, it doesn't.

That is strange. It is listed as "installs" module, so PW should take care of it. Bug in core or something strange on my install method?

I installed the proces module and now the edit link works and opens field, but the text still isn't shown/rendered on page...

Which text is not shown and where? Editor doesn't load value when editing.

I'm on a other install with no languages. Still doesn't output the body text when using echo $fredi->body. Just the edit link.

Oh, it shouldn't :)

$fredi->body outputs just the link, you render the content yourself with $page->body. This allows you to put the link wherever you like.

Share this post


Link to post
Share on other sites

The body text isnt shown on the page just an edit link instead of the body text.

Ah now I get iz. Think it wasnt too clear about from your example.

Share this post


Link to post
Share on other sites

That is strange. It is listed as "installs" module, so PW should take care of it. Bug in core or something strange on my install method?

Well, the process module doesn't have diabled install button so something is wrong.. :)

ProcessFredi and FrediProcess are different modules, so it can't work ;)

  • Like 1

Share this post


Link to post
Share on other sites

Well, the process module doesn't have diabled install button so something is wrong.. :)

ProcessFredi and FrediProcess are different modules, so it can't work ;)

Oh boy :) Thanks for this.

I have few tweaks coming, so will commit that fix with those.

Ah now I get iz. Think it wasnt too clear about from your example.

I added extra note for this case. Also will make better examples for official readme that is currently baking.

Share this post


Link to post
Share on other sites

Multilang fields should work now too and also fixed the problem with installation.

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
      This is a new module that 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) 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.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      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

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...