Pivot 1.40 beta
13:41We’ve released Pivot 1.40 beta. Please note that this is a beta release, so it might contain smaller or larger bugs. If you’re not comfortable using beta software, please wait a short while until we can release 1.40 final as a stable release.
This version contains a few new features:
- Comment Moderation (If you turn this on, new comments will not show up on your weblog, until you’ve approved them. You can enable this from Administration>Configuration)
- Greatly improved Metaweblog API support (so you can post to your Pivot log from other applications)
- A new ‘Registered Visitors’ administration screen, so you can disable, verify and delete them.
- The pages for Visitor Registration, Pivot errors and ‘self registration’ are now themeable.
- There are other smaller fixes, the details of which can be found in the changelog.
If you're new to Pivot, you should get the full version below, and read here on how to get started.
There are two upgraders. One for if you're upgrading any version from 1.0 to 1.30 RC, and one for upgrading 1.30 final installations. If you're upgrading, follow these steps:
- Get the updater that's appropriate for what you're running currently
- Extract the files on your computer
- Make a backup of your website. really.
- Upload all the files, overwriting the ones already present.
- Download the upgradechecks tool, unzip it, and upload to your pivot folder.
- Open pivot/upgradechecks.php in your browser, and see if you have to make any changes.
- After that, log in to your pivot.
- Rebuild the index, and rebuild all files, and you're done!
The Files are here, on our Sourceforge page:
Tip: We've heard about people (mainly on OSX) who've had their FTP programs wipe the folders clean before uploading. Make sure that doesn't happen to you. And if it does, you'll be glad you made that backup like I told you to.
twelve comments:
*Comment Moderation * Great, this is the thing my educational friends want when I recommend pivot. Many Thanks
Damn…Do you guys ever sleep ?
Thanks fot this beta. Will test it soon!
Brilliant, some new features that I’ve been looking out for and some that I just want to play with!
Why wait for a stable version when you can have one with new gadgets? 
I’ve installed the 1.40 version, and i had no problems with it. Everything is working fine.
Great job, Bob (and friends) !
Hi,
I’ve installed it, and it works great. Nice these features 
.
Grtz,
Frankie
I also have installed the Pivot 1.40 beta and all went well. The upgradechecks tool is a real killer thanks :)
Just installed it witout having any troubles.
Just upgraded from 1.3 to 14 beta without a problem!
I installed it and it runs fine ‘till i try to rebuild all files. I get the following output/error:
1.07 sec: Processed 10 entries..
1.24 sec: Processed 20 entries..
1.26 sec: Processed 30 entries..
1.38 sec: Processed 40 entries..
1.49 sec: Processed 50 entries..
1.65 sec: Processed 60 entries..
1.67 sec: Processed 70 entries..
1.86 sec: Processed 80 entries..
1.87 sec: Processed 90 entries..
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 813222 bytes) in /home/weppien/public_html/pivot/pvlib.php on line 3282
Even the update search words gives the same error.
Can you help me with that?
Aha – that “fatal error” message is just like one I’ve seen in two other places using Pivot. The first one I spotted was using the NuAmazon extension (lets you insert links to books off Amazon easily), which would Preview fine but gave a very similar error from the nusoap.php file when I tried to Publish (discussed at some length in the relevant thread on the Forum). The second was just the other day when trying to check the PivotBlacklist on my old blog (still running 1.24) – instead of giving the log, I just got the same sort of error.
Perhaps there’s something host-specific going on here?
Yes, it is host specific: the host limited the maximum amount of memory for PHP to an (old fashioned) 8 mb.
Also: the forum is for support issues.
Thanks, guys! Keep up the good work.
No trackbacks:
Trackback link: