Jump to content

Recommended Posts

1) Dev Install. I also made a backup overnight just in case  :rolleyes:

2) Local Machine. Head scratcher this one!

3) No code alteration. 

4) Yes the admin account. The only account I normally use 

5) See below

6) Do you mean reinstalling the module or physically copying files across to the Blog Module directory?

I've tried to reinstall but PW says I already have the latest version.

http://imgur.com/qQPbZXQ

Just another thought, perhaps have the Cleanup Code available as a separate module could be good too?

Share this post


Link to post
Share on other sites

That image tells me you haven't finished installing the Blog module. It is step-2 of the installation. I don't know how you got the Blog pages then since you seem not to have finished installing blog. There's is a button 'Run Install Wizard' on that screen that you need to press to fully install Blog (see image below). When done, you should see a screen like the one I posted earlier, i.e. the Blog Dashboard. You don't see the cleanup menu because you haven't finished installing Blog. What happens you click on the 'Run Install Wizard' button? If this is local install, then it is just easier to start over. If you wanna go that route, I'll guide you with the cleanup...

post-894-0-34452000-1411146244_thumb.png
Edited by kongondo

Share this post


Link to post
Share on other sites

Yes, I don't know how I got myself into this predicament.
I did press the run install wizard and everything indicated that the installation went fine.

Run Install Wizard won't run now because of all the existing fields, templates etc & the installation rolls back.

I'm happy to start again.

The reason I need to start again (besides this)  is that I can't seem to add Authors under the Authors page and wasn't sure I had to do it via the Blog Module. 

I will keep an eye out on logs etc in case it happens again ... touch wood it doesn't.
Having a bad day and hoping this is the start of my change of fortunes

Share this post


Link to post
Share on other sites

Authors are not added via the authors' page. They are normal ProcessWire users with the role 'blog-author'.
 
Try the following to cleanup blog manually:

  • Copy all the code in BlogCleanup.php to one of your template files, at the very top. Save
  • Find and replace 'private function' to 'public function' in the code you just copied
  • Find public function cleanUpPages() and add the following lines to it, at the very top of the function. Save
//Get the module config data
$this->data = wire('modules')->getModuleConfigData(get_parent_class($this));

$this->blogStyle = $this->data['blogStyle'];//selected blog style (1-4)
$this->commentsUse = $this->data['commentsUse'];//commenting feature on/off
$this->templateFilesInstall = $this->data['templateFilesInstall'];
  • Add the following code to your template file, somewhere after the last } of the BlogCleanup class you copied to this template file
$bc = new BlogCleanup();
echo $bc->cleanUpPages();
  • Visit a page that uses the template file you added the BlogCleanup class to. Blog Cleanup will run but you will get lots of PHP notices. Just ignore them. You will also have to manually delete your template files (normally it would be done for you but that needs code alteration in our manual cleanup).
  • Restore you template file to the state it was before you added the BlogCleanup class. Save

You should be able to start afresh then. I am afraid I don't have any more time today to invest in this. Hope it works out.

Edited by kongondo

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks for the instructions, Kongondo!

Much appreciated!

Unfortunately, it didn't work too well for me as it didn't clean up everything (as you mentioned) and I ended up deleting entries off the CMS as the error messages dictated.

I finally managed to get it install (I think!) with 1 error message that I'm not sure is an error, as the comments table actually is created by the installation.

I've also remembered why I got into this predicament.

The very first installation I did failed because my xdebug.max_nesting_level was set to 100 and not something higher & the installation process reached that limit. 
I was meant to come back to it, but never had the time.

After I did the cleanup & increased this number to 300, I got new error messages which I worked through. which I fixed eventually.

I will also try and post the SQL I used in seperate post.

http://imgur.com/V6OExBn
 


Rollback instructions. Use at your own risk.

1) Export your site or DB first before you do anything else. Backup! Backup! Backup!

2) Run the following script

start transaction;
select * from templates where name like '%blog%';
delete from templates where name like '%blog%';
select * from templates where name like '%blog%';
 
 
select * from fields where name like '%blog%';
delete from fields where name like 'blog%';
select * from fields where name like 'blog%';
 
select * from pages where name like '%blog%';
delete from pages where name like 'blog%';
select * from pages where name like 'blog%';
 
select * from fieldgroups where name like '%blog%'
select * from fieldgroups_fields where fieldgroups_id in (
select id from fieldgroups where name like '%blog%'
)
delete from fieldgroups_fields where fieldgroups_id in (
select id from fieldgroups where name like '%blog%'
)
delete from fieldgroups where name like '%blog%'
rollback;
 
If the Rollback attempt looks fine, run a Commit version of it.

Share this post


Link to post
Share on other sites

Aah...wish you'd mentioned that xdebug issue :-). It's bitten somebody else here before. Anyway, you got there in the end. The comments field sql error can be safely ignored. I mentioned it to Ryan a while ago but he didn't seem to be able to replicate it. It has nothing to do with Blog per se, but the comments module which ships with PW...

You rollback instructions (even with the disclaimer) seem quite dangerous and I wouldn't recommend any one to use them. You are using LIKE to search. That will match other things that are not 'blog' but 'sound' like blog...Instead, use the cleanup facility in Blog :-)

Edited by kongondo

Share this post


Link to post
Share on other sites

Yes I agree with it being dangerous ... but I was in a desperate corner and I was willing to take the risk.

As for the script itself and '%Blog%' being dangerous, I do agree but that's why I also had Select statements in there for the user to check before they delete.

Hopefully no one else will have to go through what I did :)

That XDebug issue, I only recently discovered what the cause & its outreaching effect was.

Also I first installed the blog quite a while back, long before XDebug became a big issue and i was searching around for answers.
 

I definitely will have a "Cleanup" celebration later this evening with some well earned bevvies!

Share this post


Link to post
Share on other sites

Hi,

I have a question regarding logging in the Processwire Module as a Blog Author.

I created a user that is a member of the blog-authors group.

When I login to the Processwire admin page using the user's credentials, this is all I see is this.

http://imgur.com/o5hbrWG

Had a look, and it has the following error log entry.

DATE/TIME USER URL TEXT 8 seconds ago
 

2015-10-18 14:05:33 admin /processwire/page/list/?id=id&render=render&am…

SQLSTATE[HY000]: General error: could not call class constructor [pageClass=Page, template=]

The URL Link above is :

http://localhost:8888/processwire/page/list/?id=id&render=render&start=start〈=lang&open=open&mode=mode

Logging in as Admin, there are no issues with the blog.

I can do everything including entering blog posts.

There are no error log entries for Admin/Blog Module.

FYI, I have set couple of child pages of the Blog as hidden. Could this be the cause?

Share this post


Link to post
Share on other sites

Ok I worked out that perhaps the blog-author users have no permissions to see any pages.

So I'm looking at the Blog Template and it has an option to let me choose permissions. 

However, I can't seem to click on checkboxes that enables it.

http://imgur.com/K8JFQDM

Any ideas?

Share this post


Link to post
Share on other sites

This is actually ProcessWire territory and not a Blog one. :-).

I'd suggest that you search and have a read in the forums and docs how ProcessWire implements access controls. As you've figured out, access in ProcessWire is controlled at two levels; the high level (when editing a 'role') and the low level (at the template level).. Also have a good read of the info in the 'role' edit screen. This 'homework' will help you beyond Blog...:-)

  • Like 2

Share this post


Link to post
Share on other sites

Ok thanks for the Homework :)

Feel like I'm back in school again.

I've read the docs and some forum articles as you suggested.

Didn't realise you had to allocate Add-Children permissions as well on the Blog-Posts to be able to add a new Blog-Post.

(Create Page & Edit Page permissions was not enough)

Was there a reason no permissions are set by default during the initial installation?

Seems to me a Blog-Author role implies it should be able to create & edit Blog Posts by default.

Share this post


Link to post
Share on other sites

Was there a reason no permissions are set by default during the initial installation?

Seems to me a Blog-Author role implies it should be able to create & edit Blog Posts by default.

Yes. Doing things the ProcessWire way....we make no assumptions (aka total freedom for end-user to implement as they wish). Some stuff, e.g. the role and demo files, Blog offers as a courtesy to get you started

Share this post


Link to post
Share on other sites

Yes. Doing things the ProcessWire way....we make no assumptions (aka total freedom for end-user to implement as they wish). Some stuff, e.g. the role and demo files, Blog offers as a courtesy to get you started

Aaah the Processwire way. Had a feeling you might say something similar.

I'm slowly getting accustomed to it nonetheless :)

Share this post


Link to post
Share on other sites

Hi Kongondo,

I've noticed there's a Quick Post section in the Posts Menu in the Blog Dashboard.

But it's not showing a field I added to the Blog Post Template.

I'm guessing I have to modify some module code to get it showing (& saving)?

Do you know which modules I have to look at?

Or is there another way that I've overlooked?

Share this post


Link to post
Share on other sites

It's not meant to show any other fields. For that, you need to edit your post as page as usual.

Share this post


Link to post
Share on other sites

I assume you meant traversing the Page Tree and entering a Blog Post as a page?

I think for a CMS administrator or a Developer, that is a fine workaround.

But unfortunately we're trying to convince bloggers to come write for our site and that particular UX in Processwire is not a great selling point for us IMHO.

I think the Blog Panel is actually a much better UX for a non technical person to enter blog entries into.

Just a shame that  adding a single custom field to it as not as straight forward.

Share this post


Link to post
Share on other sites

I assume you meant traversing the Page Tree and entering a Blog Post as a page?

I think for a CMS administrator or a Developer, that is a fine workaround.

But unfortunately we're trying to convince bloggers to come write for our site and that particular UX in Processwire is not a great selling point for us IMHO.

I think the Blog Panel is actually a much better UX for a non technical person to enter blog entries into.

Just a shame that  adding a single custom field to it as not as straight forward.

use this in combination with that and you have a strong "selling point" and/or alternative admin UX for batch editing even this module could be a solution for the "holder page" like /pw-root/posts/... to use ;)

The Blog panel serv also all posts in the postspage and all posts have a edit link on there titles....so hide the quickpost row simple via CSS...

Also make use of the simple and easy "Add New" Button and/or bookmarks so the user don't have to navigate trough the pagetree...there are many shortcuts and UI improvments possible with PW - but like everything else the choice to use them in your setup is on you!

regards mr-fan

  • Like 3

Share this post


Link to post
Share on other sites

Thanks for the valuable advice, Mr-Fan!

The custom admin module and the Batch Child Editor looks really useful. Especially the Batch Child Editor.

Just looked at some PW showcase websites featuring ListerPro and definitely on the shopping list

  • Like 1

Share this post


Link to post
Share on other sites

@FrancisChung, best way to remove manually is to literally uninstall module and remove the pages, so everything under blog in the page list should be deleted, including the blog page itself.  Then move into deleting the fields, then delete templates.  As in delete, I mean, delete through ProcessWire.  Once you have done this, empty trash on the page list.  Then go ahead and delete the templates from your templates directory via SSH or FTP. 

If you have tons of posts under blog, then use batch editor to remove them all at once. 

Just curious, 

Why are you removing this module?

Share this post


Link to post
Share on other sites

@quickjeff...his Blog install got messed up by an x-debug limitation so he needed to reinstall. He was caught between a rock and a hard place and couldn't use the 'cleanup feature' since Blog didn't finish installing due to the x-debug thing.

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

@kongondo - Since it was local best bet is to remove all the files or add the files again, perhaps something was missed.

Share this post


Link to post
Share on other sites

Update: Blog Version 2.3.5 (dev branch only for now)

Changes

  1. Fixed issue of slow loading dashboards on sites with lots of posts.
  2. Added some missing translation strings, thanks @mr-fan.
  3. Decluttered modal window, thanks @mr-fan.
  4. Some code optimisations.

I don't think there are any other pending issues. Apologies it took so long to get to this update; we got there in the end :-)

Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites

@Metadope,

In my testing, I never managed to replicate the issue you reported here. I know it's been a while but wondering if you managed to resolve your issue?

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...