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 bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
       
    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • 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.4. 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 franciccio-ITALIANO
      Hi, in wordpress homepage we can put a list of LAST ARTICLES AND COMMENTS.
      Can I do same thing with processwire?
      If yes, how?
      There is a tutorial?

      Thanks!