error upgrading

[Lionel]

When trying to upgrade, I get a database error. I guess existing tables don't get renamed

Invalid SQL:
SELECT * FROM new_adv_dyna_categoryperms;

MySQL Error : Table 'forums2.new_adv_dyna_categoryperms' doesn't exist
Error Number : 1146
Date : Wednesday, August

[Brian]

Which version were you trying to upgrade from exactly? That table should have been renamed after upgrading from beta 2.

[Lionel]

vBadvanced Blogicles v1.0 Beta 1 - 66

I just tried uninstalling it so I reinstall. It won't let me, saying it is already installed

[Brian]

It should still let you upgrade from Beta 1... If you want to just reinstall though, you would probably need to use the un-install functions from the beta 1 version of the vbablog_install.php file instead of the current version since the prefixes and such changed after beta 2.

[Lionel]

i had to use both uninstall. I quickly did a draft test as a regular user and it's no where to be found.

[Lionel]

I found the Draft entry.... but why Admin needs to approve it first? A draft is a draft and member should be able to work on it without approval. Admin should be concerned about publishing only

[Lionel]

Is there a way I could get rid of everything and start from scratch? Now that I found the draft, it gives me a sql error, adding double prefix

SELECT COUNT(*) AS count
FROM new_new_adv_dyna_posts AS posts

WHERE entryid = 1 AND posts.visible IN(1);

[Brian]

Actually, that looks more like a bug that may have been introduced in RC1. Could you try downloading the package from here again, replace your showentry.php file with the updated version, and see if that helps?

[Lionel]

That helps. But I think the draft issue is no good the way it is. If someone saves a draft, he should be able to work on it at any time without admin approval

[Brian]

You shouldn't need admin approval to work on a draft... If you go to 'My Stuff' => 'My Drafts' then you should see and be able to edit any drafts you've submitted there.

[Lionel]

That's my point. My Stuff/My Drafts does not display anything... until admin approves it, then drafts display.

And if you publish it, it goes thru as it was already approved

[Brian]

Well then... It was at least *supposed* to work that way. Looks like there is a small problem in the coding for the browsecategory.php file that is preventing that though. If you'll look in the file for this code:
else
{
$wherequery[] = 'entries.valid = 1';
}


And replace with this:
else if ($_REQUEST['do'] != 'drafts')
{
$wherequery[] = 'entries.valid = 1';
}


Then that should fix the problem and allow unapproved drafts to still be viewed. The browsecategory.php file in the download package here has also been updated to include this fix.

[Lionel]

fixed, thanks

[Lionel]

Now, in My Drafts mode, instead of saying "awaiting moderation", I think it should say "Currently in draft stage" or "Unpublished" so it does not create confusion. What would be the conditional to use so i don't have to change the phrase which is correct when out if drafts and really awaiting for moderation. like

<if condition==is a draft...>say so<else />awaiting ...

never mind, i'll catch it below the $wherequery
...
$which_stage =current phrase

else $which_stage=correct phrase... and dumped $which_stage in template

[Brian]

I'm not sure I'm following you... The "Awaiting Moderation" message just means that it has not yet been approved by an admin, but does not really have anything to do with it's draft status. There really wouldn't be a "is a draft" condition on that page either since every entry shown in that section would be a draft.

[Lionel]

You are right, it's really benign and a matter of personal choice. To me, how come something I haven't published yet is already awaiting moderation for indicator? Makes me feel admin is watching my every step. I would feel safer and would be also more useful visually to read an indicator such as Unpublished.

But like I said, it's only me.

[Brian]

That makes sense. On the flip side though, I think it was suggested that we add the 'Awaiting Moderation' text so that users would realize that their entry was still awaiting moderation and not get confused if they publish it and don't see it in the category. That message can easily be removed though or modified by editing your 'adv_dyna_entrybit_' (expanded or simple, depending on your settings) template.

[Lionel]

Awaiting Moderation text is a great idea when it is actually awaiting for it :-)
But if it's not ....

Both are needed (I know, I know, I am picky). The awaiting Moderation is so bold that it overpowers the publish link. And I tend to think it was already published, therefore awaiting ...

[Lionel]

Also if something is actually awaiting for moderation, I don't think that should reflect in the category entries count. I tested one entry, published and approved it. I did the same for another one except it was not approved. So main category should display 1 and not 2.