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 BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • 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://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 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 BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)