DragonflyCMS Projects > BlogsPlus > BlogsPlus 9.1.4 > Community Forums > Phoenix Netology
Forum Index > Community > BlogsPlus

BlogsPlus 9.1.4 Reply to topic


Seems to be working well although I've noted two issues:

1. Deleting the thread in the forums module doesn't remove the blog. I suspect this one may be tricky to solve without modifying the forums though so no worries!

2. This Blog didn't get the blog link posted......

One small feature request if I may - would it be possible on installation to add all historic blogs to the forum?

There can be only one

Please enter your server specs in your user profile! 😢


Very odd that the link was omitted, or was it edited out by the topic owner?


There are a couple of unresolved issues,

(a) Yes, in deleting the forums topic, there is no way of automatically knowing about the blog entry, for now. I've been stewing over that one for the past week but steered clear of adding an extra column to the topics table. It is the logical way to deal with it, much like I did with the ranks table for supporters, except forums is a more complex beast. Anything you do there will take you away from standard forums and add an extra load to forum functionality.

For now, your best option is to instruct moderators to click the blog entry link and delete from there rather than deleting the forum.

(c) Your third point can be done, but I was reluctant to mess with the install process. I'm thinking a special admin link that provides the option, after install, and which could be run at any time of admin's choosing - a simple check of which option is in use, then cycle through the blogs listing and if topic_id is zero for a blog entry, then auto-create a forum topic for that entry.
* the upside is that it will pick up topics missed like in your second point above.
* the downside is that it will re-create a topic you have deleted, until point (a) is resolved.

(d) Past comments will also need to be added if the option is chosen for blog comments in the forums.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):


I agree that (a) is no big problem - just needs moderator education!

I also like your suggestion for (c) but agree that it needs (d)!!! The issue with recreating blogs is no problem given that it should only be needed once and the admin can ensure that all the bad ones have been cleared out first ....

There can be only one

Please enter your server specs in your user profile! 😢


hmm, funny that I seem to have jumped from (a) to (c) Confused

Anyway, I shall implement (c) and (d) - (b) obviously wasn't important anyway Laughing

I might also take the opportunity to begin an admin ReadMe section in this module as well.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):


Okay, past forum topic generation is working for old blog entries if you have either of the 2 forum options selected. If you have none left to convert or if you have the blog only option selected, it simply won't let you proceed, and tells you why.

I just need to add in conversion of old comments to posts where appropriate.

Each topic generation uses 12 queries, plus there will be more for comment conversion, so I've included a sleep function to minimize server load with large numbers of blogs on large active forums. Sleep duration can be varied in the "Config" section (default 5000 microseconds).

There's a progress bar to keep you informed so you aren't alarmed by the time factor.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):


Sounds very good!

There can be only one

Please enter your server specs in your user profile! 😢


Version 914b is in the pre-release downloads, and also includes an admin ReadMe.

If using with your existing v9.1.4, you will need to add an extra field to the cms_config_custom table,

Blogs . sleep_delay . 5000

Then delete the cached MAIN_CFG file so that it regenerates.

You may wish to increase sleep to 1000000 (i.e. 1 second) for tests, which is no big deal since there are only 17 blogs on rearparty. At least you will see the progress bar working.

If you show SQL Queries while in admin, don't be alarmed by the large number and times displayed - that's because there is no page refresh during the process - the sleep delay ensures that it's not a true reflection of instantaneous load on your server.

I've tested successfully but still recommend backing up the existing cms_blogs first. I've been testing by posting topics to a dedicated blogs forum and just using the moderator panel to delete them.

Once finished, try to run it again - it will politely tell you to rack off.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):


Phoenix,
Just done all that on rearparty and it seems to work like a dream so thank you once again. A great module that seems very popular with our users - see this one for instance!!

I guess you must just about be ready to go live on this module?

There can be only one

Please enter your server specs in your user profile! 😢


Very impressive story Smile

I've done a little compliance tidying up, IE adjustments, and simplified the blog display on the main page - no more image to open an entry, just a click on the left side will be sufficient (denoted by the hand cursor). It serves to simplify the code, increase real estate on the title line and reduce image loading, albeit minisculely.
nukebiz.com/Blogs.html

Most changes at DF and here are targeted at foreground image elimination/reduction in line with reducing page generation which eventually targets PDAs etc.

So, yes, ready for live distribution - thanks for the testing Very Happy

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):


Released - simply cannot get the progress bar to display incrementally in the IE browser, but increments nicely in FF.

Also had to provide for Windows servers running PHP4 since the usleep(x) function doesn't work, so Convert reverts to sleep(1) in that instance i.e. 1 second per topic. It's slower, but guaranteed safer if there are conversions on large, active, windows based sites.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

All times are Australia/Adelaide


Jump to: