Jump to content

Recommended Posts

I'm not at a place where I can look in the code right now, so I'm going to go back and do that later. But initially I'm thinking that Apache took over this request: /ot/processwire/&modal=1 ... because there is no "?" in the URL So it's not a valid URL, at least not one that PW will get. Do you know if PW or AdminBar generated that URL? I'm guessing PW since AdminBar works in 2.0, but just wanted to check if you knew. The error message you posted was from Apache rather than PW, because PW excludes itself from getting URLs it doesn't understand via it's htaccess file.

Also in 2.1, $pages->find() and $pages->children(), etc. exclude pages that you don't have access as an option in each template's settings. You can reverse that behavior in a selector by adding: "check_access=0" to the selector. I don't think that's the case here, but just wanted to mention this option.

Share this post


Link to post
Share on other sites

Ok, this helped a lot.

&modal=1 is added by AdminBar (line 280):

<?php
/**
 * Hook to take place right before a redirect occurs
 *
 * We intercept the redirect URL and modify it to add 'modal=1' to the query string
 *
 */
public function sessionRedirect($event) {
	if(!$this->page || $this->page->template != 'admin') return;
	if(!$this->input->get->modal) return;
	$url = $event->arguments(0);
	if(preg_match('/[?&]modal=/', $url)) return;
	$url .= (count($this->input->get) ? '&' : '?') . "modal=1";
	$event->arguments(0, $url);
}

If I comment $url .=... line out, then it redirects to admin page, but there is "you are logged in" notification in place. Same happens if I go directly to /processwire/adminbar/ab-sitemap/.

But if I go to setup -> templates and set that "adminbar" template manages it's access and set it to go 404 page when there is no access, then I go to 404 page. So this is definitely some kind of access problem. Maybe in page create?

<?php
// create /adminbar/ page under admin
	$abPage = new Page();
	$abPage->template = $abTemplate;
	$abPage->parent = $this->pages->get($this->config->adminRootPageID);
	$abPage->name = $abName;
	$abPage->status = 1031; // hidden & locked
	$abPage->save();

	// after that create /adminbar/sitemap/
	$abSitemapPage = new Page();
	$abSitemapPage->template = $abTemplate;
	$abSitemapPage->parent = $abPage;
	$abSitemapPage->name = 'ab-sitemap';
	$abSitemapPage->status = 1031;
	return $abSitemapPage->save();

There is no view button on adminbar pages when browsing page tree, but this must be because there is no actual template file (we set that at runtime):

<?php
// We change the filepath of adminbar template file
public function beforePageRender($event) {
	$page = $event->object;
	if($page->template == 'adminbar') {
		$page->template->filename = $this->config->paths->AdminBar . "templates/sitemap.php";
	}
}

And I get this working when I copy /site/modules/AdminBar/templates/sitemap.php to /site/templates/sitemap.php and after that edit template "adminbar" and "advanced" tab, and set it to use sitemap.php template.

So this is pretty minor issue, but not sure if I understand where the real problem lies?

Share this post


Link to post
Share on other sites

I'm thinking the problem might be in wire/core/Template.php. It caches the state of whether the template filename exists. But it wasn't resetting it when the value of filename was changed. PW will only display a 404 for a page that exists to the superuser when there is no template to render the page.  AdminBar appears to be setting the filename, but PW still thinks it doesn't exist because the previous "non existing" value was cached. I'm thinking this is it anyway. If you grab the latest /wire/core/Template.php from the PW 2.1 source, does this make a difference? I will also test locally later today, but wanted to get this posted before a call, hoping this was it.

Thanks,

Ryan

Share this post


Link to post
Share on other sites

If the above doesn't fix it, this might: Get rid of the beforePageRender hook that sets the template filename, and move it into your init() function:

$template = $this->templates->get("adminbar"); 
if($template) $template->filename = $this->config->paths->AdminBar . "templates/sitemap.php";

I think this would work in either version of PW, though have not tested. The reason I think this might fix it is because this would set the template's filename much earlier than it currently does (well before PW would have any opportunities to check whether the sitemap page is viewable). So theoretically, this should prevent it from deciding that the page isn't viewable due to lack of a template file.

Share this post


Link to post
Share on other sites

Thanks Ryan. New template.php didn't fix it, but moving that template change to init fixed it. I will commit this sooner than later to Github (will test on 2.0 first).

Share this post


Link to post
Share on other sites

Almonk: Nice work, I like it!

I have been using Adminbar pretty much last few weeks and I have few improvements in mind. One of them is "smaller UI" - no sliding "more info" tab etc. Probably less buttons (like you have). Also current modal wastes space (which is not problem on wide screen, but is very annoying on smaller resolution).

I think I will replace "sitemap" button with link to admin site (that opens sitemap there on the right page). So there would be three buttons: edit, add child, go to admin (to sitemap view).

Any thoughts people? I am having very little time besides client projects, so it will probably take few weeks before I can continue develepment.

Share this post


Link to post
Share on other sites

Ha! It was supposed to go into the admin before you changed it! :)

The smaller @Almonks' UI looks very nice :)

Share this post


Link to post
Share on other sites

Ha! It was supposed to go into the admin before you changed it! :)

Heh, I know :) That was before we could link to an single page on pagelist though. After using adminbar myself I realised that another sitemap is just confusing. Also I'm not sure how important it is to see additional info about current page through adminbar? Things like who edited last time, who can access this page etc? I start to lean towards less is more philosophy here...

Share this post


Link to post
Share on other sites

If I recall correctly, I did that expand on click just because I wanted to show more with less :D – in original UI, you had just one pencil, which you had to click to get to editing buttons and more information. I put the buttons out and put a bit deeper the more information parts.

I think that this more information could be useful, but under certain circumstances out of scope of this post.

Share this post


Link to post
Share on other sites

If I recall correctly, I did that expand on click just because I wanted to show more with less :D – in original UI, you had just one pencil, which you had to click to get to editing buttons and more information. I put the buttons out and put a bit deeper the more information parts.

I think that this more information could be useful, but under certain circumstances out of scope of this post.

Actually you recall wrong: http://processwire.com/talk/index.php/topic,56.msg235.html#msg235 (huh - that version does look ugly.. :)). Original had two buttons: open panel + quick edit.

Most common use case is by far "quick edit". After that I think what is needed is quick link to admin view - and linking to pagelist would be best option there (now that we can link to certain page on list), since that would kill the need for sitemap. I have to test different variations here... I don't think that current "toggle view" is bad solution - but even I haven't used it at all and always had trouble to find my way back to admin site (I started to use sitemap -> go to administration link).

Share this post


Link to post
Share on other sites

Ok, I have been doing site building and some content management lately (+ building data import module), so no new progress with AdminBar in long time. But I have some user feedback from this topic, clients and from myself after using this in real situation.

I am not happy with current ui. It goes over the page and I don't think that showing/hiding it is good solution, neither is the current "hide" button. Also like I talked before, I need to consider functionality again (at least sitemap is not needed). No one uses "toggle" or "advanced view" so there should be only one view. I don't like how current modal waste space. So there is lot's of little details that just doesn't seem right.

I tried to mockup how this thing should work, and I am pretty happy with the results. I dropped the adminbar to the bottom. This gives it a lot more space and more conventional shape (horizontal). Also top of the sites are often graphically busy (logos, headers etc) so top is also nice in this regard.

The other "big change" is that modal is no longer modal. It will be content area that slides from bottom to almost top of the page. So the underlying page is visible, but we are not wasting any space on sides and just a little bit from top.

And one thing I would like to try is optional quick edit. So in templates you could say for some areas that they are quick editable. Maybe something like this:

<h1 class="quickedit"><?php echo $page->title; ?></h1>

This allows quick edit functionality. Button for this shows only when there is something that is quick editable. This is something that I am thinking of, not something I will build for sure, so please tell me what you think?

I attached current mockups, but need to say few words about these: I'm not sure about the icons (probably will settle with something more simple and single color). Also I probably will remove or change location of logout. Link to admin will be used a lot, so it needs to be easy click and without possibility to miss and hit logout accidentally. And if someone wants to help me with UI graphics (adam, almonk, anyone) you are more than welcome.

post-79-132614277816_thumb.png

post-79-132614277845_thumb.png

Share this post


Link to post
Share on other sites

Great thinking with these updates. It makes a lot of sense what you are saying about the location of the AdminBar. I also like your new approach non-modal overlay–can't wait to try it out. :) One thought is that some may prefer this same type of horizontal admin bar anchored to the top of the screen rather than the bottom, but I think it will depend on the person (maybe a configuration choice?)

The quick edit sounds great. I'm interested to learn more. If you implement this, I wanted to mention that you can now optionally pass a field name to the editable function(), which may make sense with the quick edit capability:

<?php
if($page->editable()) { /* page is editable, same as before */ }
if($page->editable('field_name')) { /* New: field_name on page is editable */ }

Down the road, PW will support field-level permission granularity. Meaning you can let a user edit some things on a page and not others. It doesn't support that yet (beyond template, parent and sortfield), so I mainly mention this for future-proofing if you want to use it. Currently this editable('field_name') function only applies to template, parent, and sortfield to see if the user has access to modify those properties of the page. It returns true for everything else.

Share this post


Link to post
Share on other sites

I'm not sure about 'quick edit' functionality - adminbar should strive to make everything quick to edit in my opinion ;)

That said, I do like the idea of somehow integrating edit in place functionality somehow - http://www.aloha-editor.org/ < this is a nice little add on that is being used a lot recently, notably in Locomotive CMS (http://www.locomotivecms.com/)

Other than that, love the new look and UI for adminbar, although, as Ryan said, I'd prefer it at the top ;)

Share this post


Link to post
Share on other sites

http://www.aloha-editor.org/ < this is a nice little add on that is being used a lot recently, notably in Locomotive CMS (http://www.locomotivecms.com/)

Exactly the implementation I was looking for! Feels very fast for quick edits (you can test it by logging in to locomotive demo site, and there top right corner -> view website). Not sure how much convenient it is in real life than default adminbar edit (so is it worth to have two different methods for quick editing the content). That really makes a good demo/sales effect though ;)

I will probably switch the bar to the top.

Share this post


Link to post
Share on other sites

Aloha Editor looks great. I've not had time to investigate the technical details of it yet, but based on what I understand so far, we might need to create a new Inputfield module to support this?

It looks to me like locomotive is using TinyMCE on their admin/back end.

Share this post


Link to post
Share on other sites

I've taken a closer look. This page answered a lot:

http://www.aloha-editor.org/wiki/How_to_install_Aloha_Editor

Implementation on the front end looks easy. Not yet sure what to do on the back end, maybe the same thing. There would be a couple modules involved:

The first AlohaEditor.module would be an autoload module that triggers itself when it sees that you are viewing a page on the front end that you have access to edit (hooking in via Page::render). It would insert AlohaEditor's <script> tags before the closing </head> tag in the markup. It would also look for an ajax post and handle any submitted changes. I can communicate it better in code than text, so here goes:

<?php

class AlohaEditor extends WireData {

    public static function getModuleInfo() {
        return array(
            'title' => 'Aloha Editor',
            'version' => 100,
            'summary' => "Makes fields editable on the front end",
            );
    } 

    public function init() {
        // if it's not editable, don't setup any hooks
        if(!$this->page->editable()) return;

        // attach hook to Page::render
        $this->addHookAfter("Page::render", $this, "pageRender"); 

        // check if changed data posted
        if($this->input->post->aloha_save) {
            $field = $this->input->post->aloha_field;
            $value = $this->input->post->aloha_value; 
            $this->page->setOutputFormatting(false);
            $this->page->set($field, $value); 
            $this->page->save($field); 
            $this->page->setOutputFormatting(true); 
        }
    }

    public function pageRender($event) {
        $out = $event->return;
        $out = str_replace("</head>", "script tags </head>", $out); 
        $event->return = $out;  
    }
}

Next would be a TextformatterAloha module that you select as the "text formatter" for any text-based field types that you want to be editable on the front end. (this is in each field's settings). It would wrap a <div class='aloha-editable'>...</div> around the output of any fields you wanted to be editable (when it sees that you have access to do so). i.e.

<?php

class TextformatterAloha extends Textformatter {
    public static function getModuleInfo() {
        return array(
            'title' => 'Aloha Formatter',
            'version' => 100,
            'summary' => "Select for any fields you want to be editable",
            );
    }

    public function format(&$str) {
        if(!$this->page->editable()) return;
        $str = "<div class='aloha-editable'>$str</div>";        
    }
}

The last part would be creating another JS file to be included with the ones AlohaEditor comes with. That JS file would activate AlohaEditor for any fields that have the aloha-editable class. And it would work with Aloha Editor's callback and getContents() function to send the jQuery ajax post to the current page whenever a change is made (where it would get saved in the AlohaEditor.module's init function above). I need to do more reading at the Aloha site before I could code up an example of that.

This is all just written in the browser, so some of it may not be quite right. If anyone wants to take a stab at this I'll be happy to help. It also seems like this might be a natural fit in AdminBar, though I'm not sure–what do you think Antti? AdminBar's existing method may still be preferable for several reasons, but Aloha may be good for those times when you want to edit content in the context of the site's exact placement and styles. Sites are usually designed for presentation not editing, so it's one of those things that would be useful sometimes and not others, but definitely seems like an interesting option.

Share this post


Link to post
Share on other sites

Ryan's solution looks nice and clean. I was first thinking implementation without that textformatter, so person who creates html template can add that on wherever he thinks quick editing is reasonable. But using textformatter here is much cleaner solution!

I am still worried if this is good in overall, compared to modal-type of editing. Quick edit only supports text fields, where processwire sites (at least those that I have build) have lot's of other fields too, mainly page-fields. Of course we can add two different edit modes, but is that really convenient? Other option is to ditch modal editing all together and simply only offer aloha inline editing + real admin.

Anyway, I got working version of the new ui ready yesterday. It will get some more polish, but I find it already more pleasing to use than old one. "Sliding" is nicer than modal in this situation. You can grab this version from: https://github.com/apeisa/AdminBar/tree/AdminBarNew

Share this post


Link to post
Share on other sites

Did some comparison between adminbar and locomotive's inline editing. Not so impressed with locomotive's current implementation anymore. Clicking edit button creates full page refresh and again saving (or clicking "done editing") creates another. It doesn't feel fast and it's not fast. I think editing with current way adminbar is done is much quicker (it loads editing page in background and shows it in iframe), and creates page refresh after you hit save. Also things like saving or canceling editing are much clearer in adminbar.

Of course inline editing could be done without any page refreshes at all, and that should be quicker than adminbar's current implementation. I need to think about this a little, but it seems that I won't be getting into that inline editing thing after all. It is nice demo and great for small and simple sites, but it just don't seem to bend very well for flexibility that pw offers. I think it really is more confusing than beneficial for many reasons. Situations where someone should really consider implementing inline editing are when they are building something like drupal gardens is for drupal.

Share this post


Link to post
Share on other sites

I don't even think that inline editing has any place in PW system; not with the multiple inputfiled types, not with this simple API. Current solution in Locomotive (Aloha) allows to edit only text fields, and on current page. I, on the other hand, take data from multiple pages (in page tree) almost on every page (on the front-end), so the inline editing would allowed only on little fraction on fields – not to mention I imagine it quite cofusing for end-user, imagine this:

You have some listing of blog posts. Why can't you edit their titles here on the list page? You would have to click the blog post and edit it there. Or, you have images, you couldn't edit their description, because 1., it might be javascript slideshow for instance, and that would get cumbersome, not to mention 2., you can't use aloha editor on image description, because it's not textfield.

In-place editing would have to be much much much more tied into system, and templates would just get plain messy, just to let JS know  what parts are editable with what type of editor, not to mention, that you'd have to have special CSS for most of the items, because just adding 5px border would mostly just fuck up (my) CSS, not display what content you're editing.

So I believe Aloha is currently no-go, simply because making inplace editing for PW with the wide range of possibilities is god damn straight up inhuman task, so... there.

Share this post


Link to post
Share on other sites

Nice AdminBar updates! I've installed it on the site I'm developing now and I know the client will love this.

I'm not suggesting that inline editing would ever be a replacement for existing editing tools. Nor am I suggesting it should be part of the core (just a 3rd party module option). And I probably wouldn't use it myself. It goes against CM accessibility best practices– content shouldn't have a specific presentation context dependency. But I do think there are some situations where it would be a useful option to provide... like when the needs are really simple and the client is your Grandma (and I can think of other cases, few and far between).

But the main reason I like it is...

Putting on my salesperson hat– If I going in to pitch a proposal for a site and I can show the client that they can update their address, phone, headline, directions, etc., right in the page where it appears, then I've just sold the decision makers. Many times, these people don't understand content management best practices and may not even know exactly what a CMS is (and rarely are they the ones that will actually use it). They understand the concept of print and printing-presses, and they don't like thinking beyond those boundaries. Dynamic content is an abstract concept that's understood only as a buzzword. These are the folks I have to convince. Despite the drawbacks of inline editing, these people will "get it" immediately, and I will be their problem solver. When the next guy comes in pitching the benefits of taxonomies and nodes, then they won't even be listening.

So whether or not the inline editing capability is useful or good is debatable. But I think we can all agree it's at least compelling eye candy that can help to market a product and connect with a broader audience.

  • Like 1

Share this post


Link to post
Share on other sites

I also meant to add that I think this thing would best be developed as a module on it's own. I know that this came up in talking about AdminBar, but AdminBar's utility is clearly far greater than that of any inline editor. Or to word it differently, I would install AdminBar on all sites, but I would only install Aloha as another option in some cases. The two could of course also run together, but it seems like Aloha should probably exist as an independent 3rd party module rather than integrated into anything else (if that was even a consideration). If anyone else decides to develop an Aloha editor module, let me know. Otherwise, I will probably put one together at some point in the near future because it seems like it will be pretty easy to do (building from the code posted earlier).

I mentioned above that AdminBar is something that I would install on all sites (and I'm guessing more than half of others would too). I think it might make sense for AdminBar to be a core module (maybe with 2.1 or 2.2 release?). That way it would be ready to install (1-click) for anyone that installs ProcessWire. Antti, would you have any interest in this, or would you prefer to keep it separate?

  • Like 1

Share this post


Link to post
Share on other sites

Great discussion. This is really interesting question. One article I remember reading from this topic is here: http://allinthehead.com/retro/357/the-lure-of-on-page-editing (great comments also).

You have some listing of blog posts. Why can't you edit their titles here on the list page? You would have to click the blog post and edit it there.

This is true. But it is also true on current AdminBar implementation and it is also true on real admin site: you cannot edit blog posts when you are editing blog listing page.  Non-tech people would probably find the actual blog post easier by clicking blog post, than by looking for children pages (or somewhere else - you just have to know) in admin site.

Or, you have images, you couldn't edit their description, because 1., it might be javascript slideshow for instance, and that would get cumbersome, not to mention 2., you can't use aloha editor on image description, because it's not textfield.

Yes, special cases like these are where true admin view is much better or even only option.

In-place editing would have to be much much much more tied into system, and templates would just get plain messy, just to let JS know  what parts are editable with what type of editor, not to mention, that you'd have to have special CSS for most of the items, because just adding 5px border would mostly just fuck up (my) CSS, not display what content you're editing.

I'm not so sure about this. Ryan showed example code which means you don't have to do anything special in your templates. Also no need to use 5px border (special background icon on that wrapper div that TextformatterAloha creates should be enough). So you do not need anything special in your CSS neither.

Putting on my salesperson hat– If I going in to pitch a proposal for a site and I can show the client that they can update their address, phone, headline, directions, etc., right in the page where it appears, then I've just sold the decision makers.

This is exactly the same reason why I have been thinking for this. It looks damn good on sales meeting, might even give one or more "wow, that is nice" comments from audience. And depending on the site your "content editing" might be mostly small edits, typo corrections, linking and stuff like that. Then you would love tool like aloha editor. So there is also real life situations where it would be good.

I also meant to add that I think this thing would best be developed as a module on it's own.

I was earlier thinking this in realm of adminbar, and somehow didn't even think that option. I think that it would make great sense to build this separately, but in a way that they work well together. It keeps adminbar codebase clean and simple - and gives it path to grow in more "admin" direction if needed.

If anyone else decides to develop an Aloha editor module, let me know. Otherwise, I will probably put one together at some point in the near future because it seems like it will be pretty easy to do (building from the code posted earlier).

I might put some effort to this on my summer holiday (first week going, three left). It seems simple and rewarding project. Or maybe I do something after we finish the movie tonight.... ;) (edit: decided to close computer and go to bed)

I mentioned above that AdminBar is something that I would install on all sites (and I'm guessing more than half of others would too). I think it might make sense for AdminBar to be a core module (maybe with 2.1 or 2.2 release?). That way it would be ready to install (1-click) for anyone that installs ProcessWire. Antti, would you have any interest in this, or would you prefer to keep it separate?

Of course, that would be an honor actually :)

Share this post


Link to post
Share on other sites

I totally agree with Ryan on this.

I don't think Aloha is appropriate for 100% of problems, but it doesn't need to be to be useful. As Ryan says, it's a cool little utility that provides a useful function and I personally would love to see support for it.

  • Like 1

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 Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module and >= ProcessWire v3.0.0.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Advanced
      Define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Build entire dialog form in a hook
      You can hook after HannaCodeDialog::buildForm to add inputfields to the dialog form. You can define options for the inputfields when you add them. Using a hook like this can be useful if you prefer to configure inputfield type/options/descriptions/notes in your IDE rather than as extra attributes in the Hanna tag settings. It's also useful if you want to use inputfield settings such as showIf.
      When you add the inputfields you must set both the name and the id of the inputfield to match the attribute name.
      You only need to set an inputfield value in the hook if you want to force the value - otherwise the current values from the tag are automatically applied.
      To use this hook you only have to define the essential attributes (the "fields" for the tag) in the Hanna Code settings and then all the other inputfield settings can be set in the hook.
      Example buildForm() hook
      The Hanna Code attributes defined for tag "meal" (a default value is defined for "vegetables"):
      vegetables=Carrot meat cooking_style comments The hook code in /site/ready.php:
      $wire->addHookAfter('HannaCodeDialog::buildForm', function(HookEvent $event) { // The Hanna tag that is being opened in the dialog $tag_name = $event->arguments(0); // Other arguments if you need them /* @var Page $edited_page */ $edited_page = $event->arguments(1); // The page open in Page Edit $current_attributes = $event->arguments(2); // The current attribute values $default_attributes = $event->arguments(3); // The default attribute values // The form rendered in the dialog /* @var InputfieldForm $form */ $form = $event->return; if($tag_name === 'meal') { $modules = $event->wire('modules'); /* @var InputfieldCheckboxes $f */ $f = $modules->InputfieldCheckboxes; $f->name = 'vegetables'; // Set name to match attribute $f->id = 'vegetables'; // Set id to match attribute $f->label = 'Vegetables'; $f->description = 'Please select some vegetables.'; $f->notes = "If you don't eat your vegetables you can't have any pudding."; $f->addOptions(['Carrot', 'Cabbage', 'Celery'], false); $form->add($f); /* @var InputfieldRadios $f */ $f = $modules->InputfieldRadios; $f->name = 'meat'; $f->id = 'meat'; $f->label = 'Meat'; $f->addOptions(['Pork', 'Beef', 'Chicken', 'Lamb'], false); $form->add($f); /* @var InputfieldSelect $f */ $f = $modules->InputfieldSelect; $f->name = 'cooking_style'; $f->id = 'cooking_style'; $f->label = 'How would you like it cooked?'; $f->addOptions(['Fried', 'Boiled', 'Baked'], false); $form->add($f); /* @var InputfieldText $f */ $f = $modules->InputfieldText; $f->name = 'comments'; $f->id = 'comments'; $f->label = 'Comments for the chef'; $f->showIf = 'cooking_style=Fried'; $form->add($f); } }); Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By horst
      Wire Mail SMTP

      An extension to the (new) WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.4.2
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; }  
      A MORE ADVANCED DEBUG METHOD!
      You can add some debug code into a template file and call a page with it:
      $to = array('me@example.com'); $subject = 'Wiremail-SMTP Test ' . date('H:i:s') . ' äöü ÄÖÜ ß'; $mail = wireMail(); if($mail->className != 'WireMailSmtp') { echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; } else { $mail->from = '--INSERT YOUR SENDER ADDRESS HERE --'; // <--- !!!! $mail->to($to); $mail->subject($subject); $mail->sendSingle(true); $mail->body("Titel\n\ntext text TEXT text text\n"); $mail->bodyHTML("<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>"); $dump = $mail->debugSend(1); } So, in short, instead of using $mail->send(), use $mail->debugSend(1) to get output on a frontend testpage.
      The output is PRE formatted and contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection, like this one:
       
      Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      debugSend(1) - returns and / or outputs a (pre formatted) dump that contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection. (See above the example code under ADVANCED DEBUG METHOD for further instructions!)


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
       
    • By Robin S
      Sanitizer EasySlugger
      Allows the use of the EasySlugger library as Sanitizer methods.
      Installation
      Install the Sanitizer EasySlugger module.
      Usage
      The module adds four new sanitizer methods.
      slugger($string, $options)
      Similar to $sanitizer->pageName() - I'm not sure if there are any advantages over that method. Included because it is one of the methods offered by EasySlugger.
      $slug = $sanitizer->slugger('Lorem Ipsum'); // Result: lorem-ipsum utf8Slugger($string, $options)
      Creates slugs from non-latin alphabets.
      $slug = $sanitizer->utf8Slugger('这个用汉语怎么说'); // Result: zhe-ge-yong-han-yu-zen-me-shuo seoSlugger($string, $options)
      Augments the string before turning it into a slug. The conversions are related to numbers, currencies, email addresses and other common symbols.
      $slug = $sanitizer->seoSlugger('The price is $5.99'); // Result: the-price-is-5-dollars-99-cents See the EasySlugger readme for some more examples.
      seoUtf8Slugger($string, $options)
      A combination of utf8Slugger() and seoSlugger().
      $slug = $sanitizer->seoUtf8Slugger('价钱是 $5.99'); // Result: jia-qian-shi-5-dollars-99-cents $options argument
      Each of the methods can take an $options array as a second argument.
      separator (string): the character that separates words in the slug. Default: - unique (bool): Determines whether a random suffix is added at the end of the slug. Default: false $slug = $sanitizer->utf8Slugger('这个用汉语怎么说', ['separator' => '_', 'unique' => true]); // Result: zhe_ge_yong_han_yu_zen_me_shuo_3ad66c4  
      https://github.com/Toutouwai/SanitizerEasySlugger
      https://modules.processwire.com/modules/sanitizer-easy-slugger/
    • By Robin S
      If you've ever needed to insert links to a large number of files within CKEditor you may have found that the standard PW link modal is a somewhat slow way to do it.
      This module provides a quicker way to insert links to files on the page being edited. You can insert a link to an individual file, or insert an unordered list of links to all files on the page with a single click.
      CKEditor Link Files
      Adds a menu to CKEditor to allow the quick insertion of links to files on the page being edited.

      Features
      Hover a menu item to see the "Description" of the corresponding file (if present). Click a menu item to insert a link to the corresponding file at the current cursor position. The filename is used as the link text. If you Alt-click a menu item the file description is used as the link text (with fallback to filename if no description entered). If text is currently selected in the editor then the selected text is used as the link text. Click "* Insert links to all files *" to insert an unordered list of links to all files on the page. Also works with the Alt-click option. Menu is built via AJAX so newly uploaded files are included in the menu without the page needing to be saved. However, descriptions are not available for newly uploaded files until the page is saved. There is an option in the module config to include files from Repeater fields in the edited page. Nested Repeater fields (files inside a Repeater inside another Repeater) are not supported. Installation
      Install the CKEditor Link Files module.
      For any CKEditor field where you want the "Insert link to file" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "LinkFilesMenu" to the "CKEditor Toolbar" settings field.
       
      http://modules.processwire.com/modules/cke-link-files/
      https://github.com/Toutouwai/CkeLinkFiles
    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate a repeater item from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
×
×
  • Create New...