Jump to content

Recommended Posts

Glad you got it sorted. Could I suggest that you direct the Autolinks question to Ryan? Maybe there's a way around the bottleneck...How many pages were you trying to load at once, btw?

Share this post


Link to post
Share on other sites

Btw, thanks, your question made me realise that the code around the strip_tags need to be optimised anyway...That bit of code should only load when post small is set to true.

  • Like 1

Share this post


Link to post
Share on other sites

About 10 pages. When you linked me to your demos, I immediately thought it must be Textile or Hanna but it wasn't. I was surprised to see Autolinks being the issue. Obviously, the other two will add some processing overhead but nothing like Autolinks in this particular circumstance.

Share this post


Link to post
Share on other sites

Hi,

I've just installed ProcessBlog on a test install of ProcessWire and all the admin side of things appears to work without issue, however when I try accessing any of the blog pages on the front-end all I get is a 404 not found error.

I've setup with blog style 2, and the blog pages and sub-pages all show OK in the admin page tree, and in the front-end sitemap, but viewing any of them just 404s.

Any ideas on how to what's happening and fix this?

The install was on a clean PW install (site-beginner)

Thanks in advance

Share this post


Link to post
Share on other sites

Hi again,

Only possible contributing factor is on completing installation I get a database error that says:

" SQLSTATE[42S02]: Base table or view not found: 1146 Table 'testbed_processw.field_blog_comments' doesn't exist"

Would this be the cause? How to rectify it, and why would it have occurred?

Cheers

Share this post


Link to post
Share on other sites

Hi @roblgs and welcome to PW and the forums.

Did you also install the MarkupBlog module?

MarkupBlog is not necessary if you want to create your own posts.php and post.php template files, but it makes it much quicker and easier to get going and you can use those files as a starting point and style from there.

Share this post


Link to post
Share on other sites

Hi Adrian,

Not explicitly, it wasn't clear that was necessary to do so separately from ProcessBlog which said it included MarkupBlog.

If I check modules for 'Site' then I can see

Blog Post Publish Date

Markup Blog

as installed, along with process blog

If I click on either one of those names in the list I get a page showing details, an uninstall link and a submit button. Clicking submit produces a message that the module has been saved...

Blog front-end remains unreachable

Share this post


Link to post
Share on other sites

Hi roblgs,

Welcome to the forums and PW.

Apologies for not getting back to you sooner. Sorry for the 'bad' start with the Blog module.

  1. The SQL error you see is something that started happening a couple of PW versions ago. It is safe to ignore it; just reload the dashboard and it will go away
  2. Blog automatically installs both MarkupBlog and ProcessBlog, although you may uninstall the former just fine
  3. 404s usually mean something wrong with your setup (server). URLs not being found where they are expected to be. I really doubt it has anything to do with Blog per se, but we are still going to help you :-)
  • Do other ProcessWire pages work fine? (Home, About, etc?)
  • Is this a sub-domain?
  • Is your install somewhere we can view it? (i.e. not a local install)
  • Long shot, but try installing using the 'blank profile' 

Let us know how it goes.

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks for getting back to me.

I think I have it sorted, though I took the sledgehammer approach and clean installed both PW and PB.

Previously there were no blog templates installed in /site/templates, they were all in /site/modules/ProcessBlog/template-files... this time around they are all in /site/templates and at least I now get pages when I try loading /blog and so on... i.e. no longer getting a 404.

Couple of questions... the blog templates all include blog-main.inc.

My current setup uses prepend and append files, so I'm guessing that to get it working well I'll have to create a blog-main.php as an append file, based on a merger of current _main.php and the blog-main.inc... that is if all pages are to work off a consistent model...

Initially the blog pages stacked everything vertically, but I've copied 'css' and 'js' folders from the module folder to /site/templates and its producing a more expected layout... except that it mixes the layouts/contents of blog-main.inc with that of the _init.php and _main.php currently being pre/appended, but I think that will be straightforward to clean up.

Still don't know exactly what happened previously, unless an install issue with folder permissions causing some things to not be placed where they should be. That's my current best guess, although there were no on-screen error messages to indicate that... I suspect that the /site folder and its children were not writable to the extent needed.

Anyway, atlas I have something now, which is a giant step forward from yesterday, and a base on which to learn more.

Cheers

Rob

Share this post


Link to post
Share on other sites

Glad you got it sorted. The blog templates are all for demo purposes. So you can edit them as you please, or even not use them (only using their code as a reference if you are new to coding/PW...). The CSS and JS folders are intentionally not copied over...(as explained in the read me :-))..

Share this post


Link to post
Share on other sites

Hi,

Yes, I'm at the stage of feeling all at sea with a new platform, but at least with something now visible it's easier!

Will now play with templates...

Share this post


Link to post
Share on other sites

Hi,

Unable to add name to user, or to upload an image to a user.

These fields are added by the blog, as they are not present before installing the blog.

Any ideas?

The fields are displayed in the profile edit form, but after I fill the 'name' field with a text value and submit, the field is empty on reload, and no error message.

When trying to upload an image there is a red area below the image name on submit, but no error message.

Share this post


Link to post
Share on other sites

Update...

I can add a name and an image when creating a new user, but cannot do so when trying to modify the primary admin account, even when logged in as the primary admin...

Weird!

If I logout of primary admin, and login as a different admin, I can then add name and image to the primary... Seems there is an issue with doing so when trying to update yourself.

Share this post


Link to post
Share on other sites

Hi there,

I've just added this module (MarkupBlog) and I can't seem to see the Cleanup utility as described by the install instructions.

I'm logged in as the admin user and my php debug level is set to 300.

I have not uninstalled the module prior and I've just posted a blank post, in case the Cleanup option shows after inserting the first post.

Is there anything else I should be checking?

Share this post


Link to post
Share on other sites

Hi,

Where exactly are you looking for it? You should see it in ProcessBlog, i.e. click on 'Blog' in the Admin menu and you should see it in the page that is loaded.

Thanks for using Blog!

Share this post


Link to post
Share on other sites

This is the page I see when I click the Blog? 

Is this page the "Cleanup Utility" you are referring to?
Or is there a link I don't have access to and I'm blindly not seeing?

(I have worked far too many hours last few weeks)

http://imgur.com/bZThg9e

Share this post


Link to post
Share on other sites

:) ....Not sure how to answer this :-)....The answer is right there in front of you....you haven't finished installing the module. It is a two-step process. What you are seing there is step two (with very clear info :P ). Complete that (there is an install wizard button) and you'll see everything there is to see. Please read the accompanying README in its entirety to get the most of this module. A copy is here in github

Edited by kongondo

Share this post


Link to post
Share on other sites

Hi Kongondo, 

I did actually finish the installation before trying to look for the "Cleanup Utility".

I believe this is the correct state it should be in after installation (I chose option 1)?

http://imgur.com/vio6QmQ

I think the documentation was leading me astray as it was referring to  "Cleanup Utility", "Cleanup Feature" and "Blog menu item called CleanUp", but there was no clear titles or labels that that actually included the word Cleanup in the pages I saw.

I guess it wasn't clear to me that the first initialisation page also doubled up as the cleanup utility that was referred to multiple times.

I think where it got me confused was after reading "Blog Menu Item called Cleanup".

So I see a menu item on called Blog on the admin screen.

And I was expecting to see a menu item called Cleanup as a submenu item like other different Admin menu items normally have.

Except it wasn't there as expected.

I did read the README multiple times to Cleanup the confusion I was having (pun intended)  and even searched for the word Cleanup on both wizard pages.

Imagine my distraught state when I couldn't do either  :P

Thanks for the prompt reply and building the extension. Can't wait to use it!

Share this post


Link to post
Share on other sites

Glad you got it sorted. Thanks for the feedback. I will look into the wording of the instructions. The first initialisation page is not the cleanup utility if by that you mean the first step of the install. Nor is the second step of the install the cleanup utility.. The cleanup feature is accessed via a sub-menu within the Blog itself (the Process Module)...

Share this post


Link to post
Share on other sites

The first initialisation page is not the cleanup utility if by that you mean the first step of the install. Nor is the second step of the install the cleanup utility.. The cleanup feature is accessed via a sub-menu within the Blog itself (the Process Module)...

If that's the case, then there must be a bug with the installation as I don't see a Cleanup sub-menu on either the Blog itself or the Admin module

Share this post


Link to post
Share on other sites

You will only see it if you are logged in as a superuser, something similar to below. No bug related to this has been reported before. If you are logged in as a superuser and you can't see it, then something went wrong with your installation and its best that you start afresh.

post-894-0-19566500-1444512224_thumb.png

  • Like 1

Share this post


Link to post
Share on other sites

If Superuser == Admin user, then yes perhaps something went wrong during the installation.

I had a check at the logs (Modules) and couldn't see any indicator that the installation had gone wrong.

When I get a chance to do a fresh install, I will try again from scratch and let you know.

Are you aware of any clashes with other modules, besides the the Blog Module?

Share this post


Link to post
Share on other sites

I'm not aware of any clashes. What do you mean by the Blog Module? This is the Blog Module  :lol:. You probably mean the Blog Profile by Ryan? I know it appears in the modules directory so that can be confusing. 

Let us know how it goes.

Share this post


Link to post
Share on other sites

I'm not aware of any clashes. What do you mean by the Blog Module? This is the Blog Module  :lol:. You probably mean the Blog Profile by Ryan? I know it appears in the modules directory so that can be confusing. 

Let us know how it goes.

I've just tried to uninstall the modules, but because I don't have access to the Cleanup option I presume I can't uninstall the module.

Had a look at the docs, and it refers to the cleanup option ....  :huh: 

What's the best way to remove it manually?

Share this post


Link to post
Share on other sites

You can still uninstall it but it will leave behind all the pages, fields and templates it had installed before, which then won't allow you to re-install Blog. I don't know how comfortable you are with PHP and PW but you could copy the cleanup utility code to your template file and run it from there. I can show you how to do it but before that:

  1. Is this a dev install? i.e. not a production site.
  2. Is this on a local machine or on a remote server? I just can't figure out why you cannot see the cleanup Menu item.
  3. Did you alter the module code in any way?
  4. Can you confirm you are logged in as a superuser (the main admin person)?
  5. Can you show me a screenshot of what you see when you go to /yoursite /admin/blog/? admin here is whatever you called your PW admin, normally processwire.
  6. Have you tried updating the Blog modules (just overwritting the files) to see if cleanup menu item will appear?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • 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.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...