Leaderboard

Updated 2018-05-06: Version 2.0.0 released Updated 2017-03-27: Version 1.1.3 released Updated 2016-04-11: Version 1.1.2 released Updated 2016-02-26: Officially in the module directory! http://modules.processwire.com/modules/webmention/ Updated 2016-02-25: Version 1.1.0 is now released. It's been submitted to the module directory so should appear there soon. In the meantime, it's available on GitHub: https://github.com/gRegorLove/ProcessWire-Webmention. Please refer to the updated README there and let me know if you have any questions! ------------ Original post: This is now out of date. I recommend reading the official README. I've been working on this one for a while. It's not 100%, but it is to the point I'm using it on my own site, so it's time for me to release it in beta. Once I finish up some of the features described below, I will submit it to the modules directory as a stable plugin. For now, you can install from Github. It works on PW2.5. I haven't tested on PW2.6, but it should work there. Feedback and questions are welcome. I'm in the IRC channel #processwire as well as #indiewebcamp if you have any questions about this module, webmention, or microformats. Thanks to Ryan for the Comments Fieldtype which helped me a lot in the handling of webmentions in the admin area. ProcessWire Webmention Module Webmention is a simple way to automatically notify any URL when you link to it on your site. From the receiver's perspective, it is a way to request notification when other sites link to it. Version 1.0.0 is a stable beta that covers webmention sending, receiving, parsing, and display. An easy admin interface for received webmentions is under development, as well as support for the Webmention Vouch extension. Features * Webmention endpoint discovery * Automatically send webmentions asynchronously * Automatically receive webmentions * Process webmentions to extract microformats Requirements * php-mf2 and php-mf2-cleaner libraries; bundled with this package and may optionally be updated using Composer. * This module hooks into the LazyCron module. Installation Github: https://github.com/gRegorLove/ProcessWire-Webmention Installing the core module named "Webmention" will automatically install the Fieldtype and Inputfield modules included in this package. This module will attempt to add a template and page named "Webmention Endpoint" if the template does not exist already. The default location of this endpoint is http://example.com/webmention-endpoint After installing the module, create a new field of type "Webmentions" and add it to the template(s) you want to be able to support webmentions. Sending Webmentions When creating or editing a page that has the Webmentions field, a checkbox "Send Webmentions" will appear at the bottom. Check this box and any URLs linked in the page body will be queued up for sending webmentions. Note: you should only check the "Send Webmentions" box if the page status is "published." Receiving Webmentions This module enables receiving webmentions on any pages that have have "Webmentions" field, by adding the webmention endpoint as an HTTP Link header. If you would like to specify a custom webmention endpoint URL, you can do so in the admin area, Modules > Webmention. Processing Webmentions (beta) Currently no webmentions are automatically processed. You will need to browse to the page in the backend, click "Edit," and scroll to the Webmentions field. There is a dropdown for "Visibility" and "Action" beside each webmention. Select "Process" to parse the webmention for microformats. A better interface for viewing/processing all received webmentions in one place is under development. Displaying Webmentions (beta) Within your template file, you can use `$page->Webmentions->render()` [where "Webmentions" is the name you used creating the field] to display a list of approved webmentions. As with the Comments Fieldtype, you can also generate your own output. The display functionality is also under development. Logs This module writes two logs: webmentions-sent and webmentions-received. Vouch The Vouch anti-spam extension is still under development. IndieWeb The IndieWeb movement is about owning your data. It encourages you to create and publish on your own site and optionally syndicate to third-party sites. Webmention is one of the core building blocks of this movement. Learn more and get involved by visiting http://indiewebcamp.com. Further Reading * http://indiewebcamp.com/webmention * http://indiewebcamp.com/comments-presentation * http://indiewebcamp.com/reply

I just pushed an update to BatchChildEditor that fixes the issue with setting a custom field separator - I made some variable name changes after my final testing for that feature and didn't change all as needed. Everything should be working on that front now if you really feel the need to use tabs. I just tested again with a tab separated setup like in your example above and it is working fine - although I see that you got the patch for supporting MapMarker in CSVImport to work also, so you may not need my module anymore anyways. I would like to point out one advantage though - the ability to predefine csv column to field pairings so that you can make it easier for your site editors to import future addresses.

Hi, Adrian, sorry for this! Next time I will do this in a new post. mea maxima culpa!

Adrian, read Mikel's correction above. Mikel, next time you want to say something this important, do it in a new post so people know about the change

Hello everybody, I finally made it up: The project, still in development, is using Adrians nice module "Protected Mode". This module, if set to protected mode, seems to prevent the next() and prev() methods from working correct. problem solved. PS: After going through the "Protected Mode" module I wonder HOW this module can interfere with the next() and pre() methods... PPS: Now it gets really interesting: IT IS NOT "Protected Mode" module causing the next() & prev() methods to return NULL || nullPage object. the dependency I detected meanwhile is if the current user is logged in or not: anonymous user (aka "guest") --> everything works fine logged in user --> methods return NULL I will keep working on this one...

Hi sambadave, as far as I know you don't have to upload the file again. You could go into the files folder and delete only the generated versions of the images. For example if there is an image "image.jpg" and it has generated versions like "image-600x400.jpg" and so on, you can search all images with "-600x400" delete them and after reloading the site, ProcessWire generates new versions of this image. You can try it out, but be carefull not to delete the original. Maybe make a backup before and be aware, that generating a lot of images could lead to a timeout when reloading the page, so you have to reload the page several times. Regards, Andreas

GitHub page is up, see first post.

Hi, ok, I forgot to mention that I need to use some of the "_init.php" vars in the _header/_footer.php inside ./pages2pdf. I tried to include the _init there, and then in the template as you suggested, but a simple var_dump for one of the "_init" variables returns empty. to give you a bit of background; I use thiis approach: https://processwire.com/talk/topic/10447-using-translatable-strings-across-template-files/#entry99012 for the template translation thing, but somehow the templates inside pages2pdf are ignorant of the "_string.php" file. I have some "translateble" strings in _header/footer.php, but they're ignorant of the translations. cheers Tom UPDATE: Ok, after some more debugging I see that the include_once('../_init.php') works like you presumed, the vars are there. something else must interfer with the translation thing, at least it is not caused by a not-working include. sorry for the bother. UPDATE 2: After even more debugging and testing; the _init needs to be included in all three php files: _header.php, page.php, _footer.php - it seems to be scoped to that file alone where it is included. I somehow was expectng that the incude in the _header.php alone would be enough, but after reflecting how the PDF is looking -- where _header and _footer are repeated on every "page" of the PDF -- it makes sense that this didn't work out. However, I think having three identical includes that are repeatetly called during the creation of the PDF is not really the best way to go about this, even if it now works… ?

Just in case someone stumbles across this in the future - forceLogin() is now available (since 2.6.8): https://processwire.com/blog/posts/processwire-2.6.8-brings-new-version-of-reno-admin-theme-and-more/#new-session-gt-forcelogin-user-method-to-login-user-without-a-password

I'm using almost the same setup, but my "t" function handles context too. The good thing is that _strings.php can be copied to your next projects too. function t($text, $context = 'General', $textdomain = '/site/templates/_strings.php') { return _x($text, $context, $textdomain); } _strings.php: // Search _x('Search site', 'Search'); _x('No matches', 'Search'); // Forms _x('From', 'Forms'); _x('From email', 'Forms'); _x('To', 'Forms'); ...

Hey, I think it's time to remove "templates-admin". In my opinion the shared functionalities which are still used by Reno and Default Admin Theme should be put in a separate plugin ("AdminTheme") or a core class ("AdminTheme.php") and the old "templates-admin" should be removed. To prevent that No admin theme is installed there should be a check if you try to uninstall an AdminTheme. And AdminThemeReno shouldn't have DefaultAdminTheme as dependency anymore but only "AdminTheme" class. This just makes more sense in my mind and prevents questions like this (which are completely understandable): https://processwire.com/talk/topic/10329-why-admin-theme-is-in-2-folders/ and questions about the old theme randomly popping up. As Ryan wants ProcessWire to be usable without AdminTheme, too, it's probably the better way to put the stuff in a module (as mentioned above) which can't be uninstalled (unless you know how to force uninstall modules). Please put this on the list for 2.7... Thanks, Nico

I think it would be a nice idea to add an image/field count to these inputfields. Something like below, where it says '(12)'. For me this would be a handy little addition.