As I mentioned Thursday, Mango's 1.5 release broke my Related Entries plugin. I found the time to fix it on my train ride home last night, so this morning I'm releasing the update.
While I was in there fixing the bug, I also found a way to improve the save/update process that the plugin is manipulating, so it should also be faster by a significant margin.
- Plugin:
- Related Entries
- Version:
- 1.1.4
- Requires:
- Mango Blog 1.5+
- Auto-install URL:
- http://fusiongrokker.com/get/RelatedEntries
Posted in
Mango |
My projects
| 1 Response
July 10 2010
With Mango 1.4.2, logging was moved from the insecure (using the default location, anyway) file-based logging to database logging. This was a great security improvement, because then nobody could just pull up your error and warning logs and get a hold of semi-secret information that might give a hacker clues that help them gain access to your site.
However people complained that too much was being logged, causing the database to grow at a rate faster than they thought was reasonable. To combat this, a setting was added to control how much information gets logged in the event of a plugin error. By default, only summary information is logged. This tells you which plugin is throwing the error, but does not include any of the information you might need to debug the error. If you're a plugin developer — or even just trying to troubleshoot a problem on your blog — it would be really helpful to have that detail information. Here's how.
In the root of your blog's folder, find config.cfm and open it up. It's going to be a jumbled mess of xml (without line breaks) but don't worry, the stuff we want to change is all the way at the end. Just jump to the end and start scanning backwards.
Find this section:
<node name="logging">
<map>
<entry key="level" value="warning"/>
</map>
</node>
…And change "warning" to "debug". To make the change take effect, go into the Cache section of admin and click the Reload Configuration button. Until you do this, errors will still only have summary information logged.
Do note that this will cause a lot of information to be logged for errors, which could cause the database to grow significantly if your blog is throwing lots of errors. I would encourage you to use something like LogViewer to inspect and clear the error logs regularly.
Posted in
Mango
| No Responses Yet
July 09 2010
I've gotten a few bug reports about this so I figured it was worth mentioning. Mango 1.5 changed something small with the way that plugins can modify a post during the save process, which breaks Related Entries. I'll be working on a fix as soon as time permits.
Posted in
Mango |
My projects
| No Responses Yet
July 08 2010
A couple of improvements flew under the radar in the recent point release of Mango that I thought were worth mentioning so that you know you can take advantage of them. I believe both may be new to blogs using SQL Server to store their data, but were functional in Mango 1.4.x for blogs using MySQL.
First, the new database-logged errors and warnings are now properly exposed for SQL Server users, which means that LogViewer will once again give you access to view and delete log information. Unfortunately, if you were using LogViewer the problem that was keeping it from working in 1.4.x was something that itself was being logged, and frequently. If that's the case, the first time you get back into LogViewer, it'll have a lot of errors, which may end up being so much content to deliver to the browser or so much for your browser to render that it crashes. If that's the case, you can delete all of the records from the log table and that will make using LogViewer more manageable.
Second, Mango 1.4 also added revision tracking to posts and pages; and once again, it seemed not to work with SQL Server. I believe both of these features were affected by a single deeper problem. But now that the bug is fixed, you should see a new section at the bottom of the edit-post and edit-page pages that shows a list of revisions of the entry, if it's been edited at least once since the Revision Manager was added. From there, you can roll back to or compare with any previous revision of the same entry.
Posted in
Mango
| No Responses Yet
July 07 2010