kongondo

Module: Blog

Recommended Posts

Hi @bot19,

Welcome to the forums. The second error is, yes, as a result of trying to install again whilst there are left over components from the first install that failed. I am not sure why the first one failed. I have never seen that error before. As for cleaning up, normally, if the install had worked, you would have a cleanup menu. Since install failed, that cannot help you now. I have an old gist for such eventualities. I believe it should still work. Please use it to cleanup and then try to re-install Blog. If it fails again, we will debug the issue step-by-step.

Edited by kongondo

Share this post


Link to post
Share on other sites

Hey @kongondo, thanks! I've been browsing here for a while but couldn't contribute much as a newbie so I've only just signed up now.

I downloaded the cleaner file, changed it to .php, associated it with a page and accessed the page to run it (only way I knew how to do this). It seems successful from the screen attached. 

I guess we will need to debug it. Thank you for your help!

I'm using browsersync so it has an external port I can provide for you, as well as access to the CMS. I'm happy to do it together at a time when you're free, as I can make any changes you need  to debug.

Thanks again very much!

Screen Shot 2017-10-30 at 11.05.55 am.png

Share this post


Link to post
Share on other sites
7 hours ago, bot19 said:

I downloaded the cleaner file, changed it to .php, associated it with a page and accessed the page to run it (only way I knew how to do this). It seems successful from the screen attached.

Great. Try and re-install Blog and we'll take it from there.

Share this post


Link to post
Share on other sites
22 hours ago, kongondo said:

Great. Try and re-install Blog and we'll take it from there.

@kongondo

Ah, sorry I just re-read my previous post and noticed I forgot the most important part: I did try a reinstall, but encountered the same error as before :(

Also, the external URL I was talking about only works on the same wifi. If you need to dig around I can work something out. Let me know what's next.

I'll have a look too and see what I can understand.

Thanks!

Share this post


Link to post
Share on other sites

Hi @bot19,

I've been a bit busy with other stuff. I see from your other thread that the issue is not Blog-specific but a general ProcessWire issue. Let's talk there.

Share this post


Link to post
Share on other sites

Hi all. 

I am intending to ONLY support ProcessWire 3.x starting from the next version of this module. Please have a read here and let me know what you think. Thanks.

  • Thanks 1

Share this post


Link to post
Share on other sites

Hi Kongondo!
I am really liking your Blog module (v2.4.1). And I have a question (processwire 3.0.62):
Under the section for Tags, I have a child tag that is parented to /tags/
Then I created a grandchild tag and it is parented to /tags/ but I want to change its parent to /tags/child/

When I try to do so, the UI only shows parent /child/ and when I save I get an error saying that the parent should be /tags/child/

Do I need to do something extra? Or is the parenting child to grandchild broken somehow?

Share this post


Link to post
Share on other sites

Welcome to the forums @Orodreth

Blog does not support grandchild tags, hence the error. I have no current plans to change this behaviour, unfortunately.

Share this post


Link to post
Share on other sites

Love love love your blog module. I have used it multiple times on sites I have built for clients. Recently ran into a weird issue. I installed your latest version of your blog module on latest processwire. When I got to save the settings in the blog quick settings tab, they dont save. The fields reload blank. Any idea?

  • Like 1

Share this post


Link to post
Share on other sites
On 12/6/2017 at 4:40 AM, quickjeff said:

Love love love your blog module. I have used it multiple times on sites I have built for clients.

Glad you like the module.

 

On 12/6/2017 at 4:40 AM, quickjeff said:

Recently ran into a weird issue. I installed your latest version of your blog module on latest processwire. When I got to save the settings in the blog quick settings tab, they dont save. The fields reload blank. Any idea?

I'll have a look when I update the module to support ProcessWire 3 only. Meanwhile, you could try saving the settings directly via their respective pages. Some live in the comments page, etc. Gotta run, so can't provide more info, sorry.

Share this post


Link to post
Share on other sites

I'm, having some issues after putting a site on a live server - maybe someone has an idea as to how to solve this.

 

I moved the site from localhost/pagename to pagename.tld. The blog posts show up in the frontend, so that's fine.

The issues are as follows:
In the admin area, clicking on the "Blog" Tab (which links to pagename.tld/processwire/blog/) results in " The requested process does not exist "

So there's no functionality there. I realize this is basically a 404 in the admin, not sure how to fix that though.

I'm using PW 3.0.75 and the latest blog module version off github, PHP7 on the live server.

Anyone got an idea as to how fix this?

Share this post


Link to post
Share on other sites
7 hours ago, Sebastian said:

I'm using PW 3.0.75 and the latest blog module version off github, PHP7 on the live server.

Hi @Sebastian. What's the difference between your local and remote servers? I have also not tried Blog on PHP 7. 

I'm hoping to move Blog fully to PW3.x sometime soon (maybe early 2018). Maybe then I can test on PHP7.

Share this post


Link to post
Share on other sites
11 hours ago, kongondo said:

Hi @Sebastian. What's the difference between your local and remote servers? I have also not tried Blog on PHP 7. 

I'm hoping to move Blog fully to PW3.x sometime soon (maybe early 2018). Maybe then I can test on PHP7.

Hi @kongondo. Well the difference is that localhost ist still PHP 5.6something :) and there the site runs out of a subfolder.

We're going full PHP7 on servers going forward (I'm guessing that's not uncommon now), so that's maybe something worth keeping an eye on.

I'm not sure if the problem is PHP 7 though - if I find the time i'm gonna setup a fresh page on 7, and install the blog module there - I'll report any findings here.

Share this post


Link to post
Share on other sites

Hey @kongondo - lots of warnings and notices.

I am running php 7.2. I don't see any issue with The requested process does not exist  - that sounds to me like the Process module wasn't installed properly, or the Admin > Blog page somehow has an incorrect Process assigned to. @Sebastian - can you check those?

image.thumb.png.f911a0b933f1175da38f96f1b94a4192.png

Share this post


Link to post
Share on other sites

Thanks @adrian.

I'll have a look. I currently have up to PHP 7.0. It seems I'll need an app that enables me to easily switch versions. I've tried several in the past but none of them worked well so I settled for UwAMP which does have its issues to.

  • Like 1

Share this post


Link to post
Share on other sites
On 10.12.2017 at 5:24 AM, adrian said:

Hey @kongondo - lots of warnings and notices.

I am running php 7.2. I don't see any issue with The requested process does not exist  - that sounds to me like the Process module wasn't installed properly, or the Admin > Blog page somehow has an incorrect Process assigned to. @Sebastian - can you check those?

image.thumb.png.f911a0b933f1175da38f96f1b94a4192.png

Hey adrian,

what I did is export / reimport the DB and copying the files over, as per usual.
I'd gladly check Process assignment wrt Blog, how do I do that?

thanks,
Sebastian

 

Share this post


Link to post
Share on other sites
12 minutes ago, Sebastian said:

I'd gladly check Process assignment wrt Blog, how do I do that?

In the page tree, go to Admin > Blog and EDIT and it should look like this:

image.png.61942b22b84f760dfb83f7fc3b68f359.png

  • Like 1

Share this post


Link to post
Share on other sites

Does anyone know best approach to including the featured image in the post itself? Let’s say below the rendered head of the post? I already have it setup as an option in the blog home page but not the post. 

Thanks!

Share this post


Link to post
Share on other sites
17 hours ago, quickjeff said:

Does anyone know best approach to including the featured image in the post itself? Let’s say below the rendered head of the post?

Apologies I've never gotten round to completing the documentation. Please see the options here.

What you want is post_large_image and possible the other post_large_image_* options. 

Share this post


Link to post
Share on other sites
On 07/10/2017 at 9:27 PM, zkriszti said:

I seem to have another issue, and as far as I've found out (having searched all the way through the forum), this is related to the small version of posts stripping tags. More exactly, I can't get 'post_small_allowable_tags' to work. I just can't seem to get the "view more" anchor appear.

The affected page is a blog-category view (based on the module's blog-category.php), where I get a few post excerpts from a given category, ideally with adding that "view more" tag. Which is nowhere to be found in the output. :(

The relevant parts of my template file look like this:


$options = array('post_small_allowable_tags' => '<p><a>', 'post_more_text' => 'tovább');
$content .= $blog->renderPosts($posts, true, $options);

Then the html output looks like this:


<div class="summary">
  <p>It's my blogpost and here is a 
    <a href="http://...">link to my another article in the text working fine.</a>
    Some more text, some more text, some more text.</p>
</div>

It is strange, because inside .summary I do have <p> and <a> tags, but <a> is only for the content (because there is a link in the referred article itself). But I don't have "view more" at the end of the summary.

Thank you very much for your help in advance!

 

Hi @zkriszti,

Sorry for the very late response. I have not been able to replicate this. It works fine for me as you can see in the following screens Both <p> and <a> if allowed, pass through just fine.

Without 'allowed tags'

blog-allowable-tags-1.thumb.png.657311120250d9712b21a6a7bff53e73.png

With 'allowed tags'

blog-allowable-tags-2.thumb.png.469ff23a253db929427857adfd022b82.png

Share this post


Link to post
Share on other sites

Update: Blog 2.4.2

As of today and this version onward, ONLY ProcessWire 3.x is supported.

Changelog

  1. Support for namespaced ProcessWire only (ProcessWire 3.x).
  2. All ProcessWire Comments Form Options can now be passed as as options to renderComments(). See the options here

Available now in the modules directory.

Please note that this version does not address any of the reported PHP 7.x issues.

  • Like 2

Share this post


Link to post
Share on other sites
On 06/12/2017 at 4:40 AM, quickjeff said:

When I got to save the settings in the blog quick settings tab, they dont save. The fields reload blank. Any idea?

Hi Jeff. I've not encountered this issue. Could you please test the latest (2.4.2) version and let me know if it resolves your issue? What version of PHP are you running? 

Thanks.

Share this post


Link to post
Share on other sites
On 22/07/2017 at 4:15 AM, Claus said:

I’d like to add ‘placeholder’ texts in the name, email, and text input fields of the comment function. How do I do this?

Hi @Claus,

I've now implemented this in Blog version 2.4.2. Pass the options available in Comments Form as part of the third parameter in Blog's renderComments(). E.g. 

$blog = $modules->get("MarkupBlog");
$presets = array('cite'=>'Your Name', 'email'=>'Your Email');
$options = array('headline'=> 'Say something', 'presets'=> $presets, 'presetsEditable' => true);
echo $blog->renderComments($page->blog_comments, 0, $options);

 

Edited by kongondo

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