adrian

Tracy Debugger

Recommended Posts

Hi @adrian, I've an issue to report:

Error: ProcesswireInfoPanel
exception 'ErrorException' with message 'Undefined index: HTTP_MOD_REWRITE' in .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc:467
Stack trace:
#0 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc(467): Tracy\Bar->Tracy\{closure}(8, 'Undefined index...', '...', 467, Array)
#1 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(127): ProcesswireInfoPanel->getPanel()
#2 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(81): Tracy\Bar->renderPanels()
#3 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Debugger.php(266): Tracy\Bar->render()
#4 [internal function]: Tracy\Debugger::shutdownHandler()
#5 {main}

I get this when my MAMP Pro's PHP mode is set to "CGI Mode" and the "Versions List" is turned on.

I have not found too much on this so called "CGI mode", only this:

http://documentation.mamp.info/en/MAMP-PRO-Mac/Servers-and-Services/Apache/

As far as I can see, this mode means the cgi_module is used, so I get the error, but when MAMP Pro's "module mode" is used instead, all is fine. According to PHP Info REDIRECT_HTTP_MOD_REWRITE is on, so it seems to be a strange issue to me.

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @szabesz - it should be fixed in the latest version.

I also added a "*confirmed false" to the mod_security entry when we know it's definitely disabled. I am pretty sure this should be accurate, but would be keen to hear reports from you guys about this. If it doesn't have this "*confirmed false" text, and it is reported to be Off, we can't be certain because it's a sign that PHP is in PHP-FPM (CGI) mode and we may not be able to detect it. As far as I can tell if it reports it as On, then I think we can be certain of this no matter what mode PHP is in.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Adrien, "Undefined index: HTTP_MOD_REWRITE" is gone with even in "CGI mode".

About CGI mode with MAMP Pro:

in v3.3.2 I used to get:

  • non CGI mode: mod_rewrite: 1, mod_security: 
  • CGI mode: "Undefined index: HTTP_MOD_REWRITE"...

now in v3.3.3:

  • non CGI mode: mod_rewrite: 1, mod_security: *confirmed off 
  • CGI mode: mod_rewrite: , mod_security

So it does detect them properly when not in CGI mode, but just as you have noted they cannot be confirmed otherwise. It might be a good idea to use a short phrase, something like "probably not installed". What do you think? Also, the status of mod_rewrite seems to be uncertain too.

BTW, is it possible to have the Inputfield Fieldsets be closed by default? I keep getting lost when all of them are open, and they are always open even after saving the settings.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Adrian,

I upgraded to 3.3.3 this morning, and noticed that the debug bar is no longer adding rows for AJAX requests, which I need to measure. Any idea what may have broken this?

Using PW3.

Thanks :)

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Mike Rockett said:

I upgraded to 3.3.3 this morning, and noticed that the debug bar is no longer adding rows for AJAX requests, which I need to measure. Any idea what may have broken this?

Sorry Mike - looks like it was an issue with a recent change to the Tracy core. I have restored the core to an earlier commit and pushed a new version here which fixes the AJAX bar.

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian,

Apologies if this has already been asked and answered before. When using the "Editor Protocol Handler" feature, the linked error is often to a file in the file compiler cache, e.g. "...\assets\cache\FileCompiler\site\templates\home.php".

But to correct the error you actually want to open "\site\templates\home.php" for editing. Would it be possible to rewrite links to compiled files so they point at the original uncompiled file instead?

  • Like 1

Share this post


Link to post
Share on other sites
6 minutes ago, Robin S said:

Would it be possible to rewrite links to compiled files so they point at the original uncompiled file instead?

It should work that way. At least it used to work. I have disabled the compiler completely in all my sites so cannot test it quickly, but I was the first one to raise this issue an Adrian had solved it. If the issue is back, it was not intentional, I think.

  • Like 2

Share this post


Link to post
Share on other sites

I have enabled the compiler just to test it and it works as expected for me.

  • Like 1

Share this post


Link to post
Share on other sites
39 minutes ago, szabesz said:

I have enabled the compiler just to test it and it works as expected for me.

That's strange. I have the latest Tracy and PW versions, and if I introduce a deliberate error into home.php I get this:

tracy.png

Share this post


Link to post
Share on other sites
On 10/1/2016 at 11:40 PM, Robin S said:

That's strange. I have the latest Tracy and PW versions, and if I introduce a deliberate error into home.php I get this:

tracy.png

That is weird - it's certainly working for me. I think the problem is the "...\" at the start of the path.

Would you mind having a play around with the replacement code (https://github.com/adrianbj/TracyDebugger/blob/90d0fd95a5f7b77df044c4a66dc5bd01e97d41e5/TracyDebugger.module#L299-L311) to see if you can come up with a working solution. The thing that makes it a little complicated is that the Tracy guys stuck with my initial suggestion of strtr rather than going with my revised str_replace option which would have given much more flexibility since strtr won't replace the same substring more than once. What this means is that you must replace the entire path up to and including "FileCompiler/". Because yours is for some reason returning a relative, rather than absolute path, the replacement isn't being made.

Unfortunately I don't have a Windows box to test on, so I think I will have trouble reproducing, although I think it might also be the way your server is configured. I would certainly like to implement a working solution though if we can get one.

Share this post


Link to post
Share on other sites

Just spent an hour or so learning how to set-up custom scheme handlers in Arch linux to try this feature out and it's now working fine for me after a few false leads. This will really come in handy - thanks Adrian and the Tracy devs!

  • Like 3

Share this post


Link to post
Share on other sites
On 3/10/2016 at 2:00 AM, adrian said:

Would you mind having a play around with the replacement code (https://github.com/adrianbj/TracyDebugger/blob/90d0fd95a5f7b77df044c4a66dc5bd01e97d41e5/TracyDebugger.module#L299-L311) to see if you can come up with a working solution.

Hi @adrian,

I have had a look at this and I think the problem is due to the direction of file path slashes on Windows versus Unix.

You can see mixed forward and backslashes in this screenshot of the Template Resources panel.

tracy-1.png

It looks wrong but the links to the editor still work okay. Edit: apparently it's no big deal to mix forward and backslashes within a path for Windows.

In terms of the error notice links containing paths to the file compiler cache, this is because having the slashes around the wrong way prevents the str_replace in Helpers::editorMapping from replacing the necessary section of the path. I got the links to work by adding the following after line 303 in TracyDebugger.module

$compilerCachePath = str_replace('/', '\\', $compilerCachePath);

Of course this is not a real solution. But maybe there is some cross-platform way to deal with file paths?

  • Like 2

Share this post


Link to post
Share on other sites

Thanks @Robin S for looking into this.

I am bad about not remembering Windows path issues. For the most part they seem to be handled quite well by PHP and don't actually need "DIRECTORY_SEPARATOR", but I think the issue is when you're doing replacements. Could you please test removing your str_replace line and modifying 303 to the following which uses DIRECTORY_SEPARATOR on the end instead of the forward slash:

$compilerCachePath = isset($this->config->fileCompilerOptions['cachePath']) ? $this->config->fileCompilerOptions['cachePath'] : $this->config->paths->cache . 'FileCompiler' . DIRECTORY_SEPARATOR;

If that works as expected, I'll try to make similar changes throughout Tracy to deal with the mixed forward/back slash links like in the Template Resources panel.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian - sorry for the delay. The change you suggested doesn't allow the file compiler path to be successfully replaced.

For me the $compilerCachePath variable before the change is...

D:/Websites/pw3-testing/site/assets/cache/FileCompiler/

...and after the change it is...

D:/Websites/pw3-testing/site/assets/cache/FileCompiler\

...but to successfully replace the link to the editor it needs to be...

D:\Websites\pw3-testing\site\assets\cache\FileCompiler\

I originally thought my str_replace suggestion was hacky but now I see there is already something similar in the nette/tracy source so maybe it is an okay way to deal with these path issues?

Share this post


Link to post
Share on other sites

No problem @Robin S - the catch with your:

$compilerCachePath = str_replace('/', '\\', $compilerCachePath);

fix is that it breaks the paths for us Mac/Linux folks. I feel like this shouldn't be that hard to sort out, but not being able to test doesn't help.I wonder if:

$compilerCachePath = realpath($compilerCachePath);

or something along those lines might work?

Share this post


Link to post
Share on other sites
15 hours ago, adrian said:

$compilerCachePath = realpath($compilerCachePath);

This pretty much works - it just misses out the trailing slash from the original $compilerCachePath so results in a double slash in the link URL. But this could be corrected:

$compilerCachePath = realpath($compilerCachePath) . DIRECTORY_SEPARATOR;

Alternatively, slash replacement could be done conditional on what the directory separator is (thereby distinguishing Windows from Mac/Linux):

if(DIRECTORY_SEPARATOR == '\\') $compilerCachePath = str_replace('/', '\\', $compilerCachePath);

Or no conditional needed for this one:

$compilerCachePath = str_replace('/', DIRECTORY_SEPARATOR, $compilerCachePath);

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @Robin S - really appreciate you testing all those options. It sounds like you are suggesting the last option is likely the best, which sounds good to me.

Before I commit that change, could you please check that editor paths work everywhere in Tracy on Windows.

Key places to check are:

  • errors panel
  • "bluescreen" fatal errors
  • links to file/line from dumps panel entries
  • log panels (does clicking on the message take you to that line in the log file)
  • template resources - page number links from variables, functions, other files etc
  • ToDo panel
  • PW Info panel - edit the template file icon

The reason to check all these is that many of them are not built by the Tracy core editorMapping option.

Thanks again!

PS - I am not suggesting that change of yours would break them if these other links were working already - I just want to make sure that there aren't any other situations we need to cover for Windows.

Share this post


Link to post
Share on other sites

Happy to do that. I'm just about to head away for a few days but will go through systematically when I'm back.

  • Like 1

Share this post


Link to post
Share on other sites

Just wanted to let you know you guys know that there have been a few tweaks to the console panel of late - nothing major, but improvements to error handling, and also notes that say "Processing" and "Completed" so you know that your script is running and when it has completed which is very handy when you are running a script that manipulates content, but doesn't output anything.

I was also just reminded of the outstanding issues with the AJAX bar and the PW SessionHandlerDB module - I was testing something on an older site (built when I used to install SessionHandlerDB as a matter of course) and couldn't figure out why bd() calls from the console panel weren't triggering the ajax bar to load. I usually use d() from the console panel so the results are right there and you don't need to refer to the dumps/dumps recorder panel, seeing the bd() reminded me that it's still not sorted.

Anyway, just wanted to remind everyone who uses SessionHandlerDB about this in case you didn't know / forgot like I did :)

 

  • Like 3

Share this post


Link to post
Share on other sites
On 9/10/2016 at 6:51 PM, adrian said:

Before I commit that change, could you please check that editor paths work everywhere in Tracy on Windows.

Key places to check are:

  • errors panel
  • "bluescreen" fatal errors
  • links to file/line from dumps panel entries
  • log panels (does clicking on the message take you to that line in the log file)
  • template resources - page number links from variables, functions, other files etc
  • ToDo panel
  • PW Info panel - edit the template file icon

Hi @adrian - with the change, the editor paths are working properly for me in all of these places.

  • Like 2

Share this post


Link to post
Share on other sites
2 hours ago, Robin S said:

Hi @adrian - with the change, the editor paths are working properly for me in all of these places.

Thanks @Robin S - that change was incorporated into the core already, so glad it works everywhere.

Thanks again for figuring out the change that was needed and for your thorough testing!

  • Like 2

Share this post


Link to post
Share on other sites
On 9/26/2016 at 10:32 PM, tpr said:

Folks at Nette are on fire :) And adrian keeps the pace :)

Btw, what about a shorthand syntax to bd()? I always have to search the docs or my previous code to get the name of the params. Something like bd(var, title, 3000, 10) would be much simpler. In fact what I need most of the time is var, maxLength, and perhaps maxDepth. But perhaps it's just me :)

Sorry for the delay on this - just thinking about it again now.

Now that I am using the LIVE option with bd(), I think that we can override depth and length limits completely. I have been playing with a new setting that makes these calls effectively have no limits by setting the depth to 99 and the length to 999999.

Screen Shot 2016-10-15 at 12.01.18 PM.png

I have been playing with it a bit here and seems to be great. One thing to keep in mind is that because Tracy's LIVE dump method renders object/array levels as you open them, setting the maxDepth so high won't actually do anything to what you see in an object/array that has been stored by the Dumps Recorder (with Preserve Dumps checked) after a page reload, but other than that, I think it works just fine, but I would really like you guys to keep an eye on things and let me know if you notice any issues.

Finally, this change does not affect items sent to the error bluescreen or the variables in the Template Resources panel, or the PW Info panel etc - these currently still rely on the maxDepth and maxLength settings in the module config.

I am not completely convinced this is a good idea yet, but I am going to leave this checked here and see how it goes. If you try it out, please let me know if you have any problems.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! For me this should be OK but will report if something goes wrong.

  • Like 2

Share this post


Link to post
Share on other sites

hi adrian,

would it be hard to get the possibility to have multiple console windows open at a time? it would be nice in some cases (for example one to create some stuff via api, eg fields or templates) and one to delete it - would be great here for testing install and uninstall method from a new module. that way you could test things really quickly. at the moment when you open the console in a new window, it loads in the "_blank" window and if you open the next console it reloads that window instead of opening a new one.

or maybe there's already a better way of doing this?

thanks :)

update: in that case it is really easy to do that, so please don't put any effort in this if you think it could not be of use in other scenarios...

$m = $modules->get('sample_module');
$m->uninstall();
$m->install();
$m->uninstall();

update2:

i still think it would be nice to have such a possibility! or at least have the option to DISABLE the code remember feature, as this overwrites the code of the current browser tab when you open the panel again. if that would not be the case we would be able to have multiple browser tabs open with multiple tracy bars with multiple console-windows. or maybe an option that the console panel does NOT close automatically? i don't know when it closes and when not. sometimes it stays open. i have not found a regularity here...

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 daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.3. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By flydev
      OAuth2Login for ProcessWire
      A Module which give you ability to login an existing user using your favorite thrid-party OAuth2 provider (i.e. Facebook, GitHub, Google, LinkedIn, etc.)..
      You can login from the backend to the backend directly or render a form on the frontend and redirect the user to a choosen page.
      Built on top of ThePhpLeague OAuth2-Client lib.
      Registration is not handled by this module but planned.
       
      Howto Install
      Install the module following this procedure:
       - http://modules.processwire.com/modules/oauth2-login/
       - https://github.com/flydev-fr/OAuth2Login
      Next step, in order to use a provider, you need to use Composer to install each provider
      ie: to install Google, open a terminal, go to your root directory of pw and type the following command-line: composer require league/oauth2-google
      Tested providers/packages :
          Google :  league/oauth2-google     Facebook: league/oauth2-facebook     Github: league/oauth2-github     LinkedIn: league/oauth2-linkedin
      More third-party providers are available there. You should be able to add a provider by simply adding it to the JSON config file.

      Howto Use It
      First (and for testing purpose), you should create a new user in ProcessWire that reflect your real OAuth2 account information. The important informations are, Last Name, First Name and Email. The module will compare existing users by firstname, lastname and email; If the user match the informations, then he is logged in.
      ie, if my Google fullname is John Wick, then in ProcessWire, I create a new user  Wick-John  with email  johnwick@mydomain.com
      Next step, go to your favorite provider and create an app in order to get the ClientId and ClientSecret keys. Ask on the forum if you have difficulties getting there.
      Once you got the keys for a provider, just paste it into the module settings and save it. One or more button should appear bellow the standard login form.
      The final step is to make your JSON configuration file.
      In this sample, the JSON config include all tested providers, you can of course edit it to suit your needs :
      { "providers": { "google": { "className": "Google", "packageName": "league/oauth2-google", "helpUrl": "https://console.developers.google.com/apis/credentials" }, "facebook": { "className": "Facebook", "packageName": "league/oauth2-facebook", "helpUrl": "https://developers.facebook.com/apps/", "options": { "graphApiVersion": "v2.10", "scope": "email" } }, "github": { "className": "Github", "packageName": "league/oauth2-github", "helpUrl": "https://github.com/settings/developers", "options": { "scope": "user:email" } }, "linkedin": { "className": "LinkedIn", "packageName": "league/oauth2-linkedin", "helpUrl": "https://www.linkedin.com/secure/developer" } } }  
      Backend Usage
      In ready.php, call the module :
      if($page->template == 'admin') { $oauth2mod = $modules->get('Oauth2Login'); if($oauth2mod) $oauth2mod->hookBackend(); }  
      Frontend Usage
      Small note: At this moment the render method is pretty simple. It output a InputfieldForm with InputfieldSubmit(s) into wrapped in a ul:li tag. Feedbacks and ideas welcome!
      For the following example, I created a page login and a template login which contain the following code :
      <?php namespace ProcessWire; if(!$user->isLoggedin()) { $options = array( 'buttonClass' => 'my_button_class', 'buttonValue' => 'Login with {provider}', // {{provider}} keyword 'prependMarkup' => '<div class="wrapper">', 'appendMarkup' => '</div>' ); $redirectUri = str_lreplace('//', '/', $config->urls->httpRoot . $page->url); $content = $modules->get('Oauth2Login')->config( array( 'redirect_uri' => $redirectUri, 'success_uri' => $page->url ) )->render($options); }
      The custom function lstr_replace() :
      /* * replace the last occurence of $search by $replace in $subject */ function str_lreplace($search, $replace, $subject) { return preg_replace('~(.*)' . preg_quote($search, '~') . '~', '$1' . $replace, $subject, 1); }  
      Screenshot
       



    • By gRegor
      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