Jump to content

Module: Blog


kongondo

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
Link to comment
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

Link to comment
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.

Link to comment
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!

Link to comment
Share on other sites

  • 3 weeks later...

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?

Link to comment
Share on other sites

  • 2 weeks later...

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
Link to comment
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.

Link to comment
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?

Link to comment
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.

Link to comment
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.

Link to comment
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

 

Link to comment
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. 

Link to comment
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

Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
Share on other sites

  • 5 months later...

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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...