TinyPortal

Development => Support => Topic started by: Gossamer on October 13, 2010, 05:26:00 PM

Title: Article Submission Queue
Post by: Gossamer on October 13, 2010, 05:26:00 PM
Link to my site: http://markedtest.elementfx.com/forum/
SMF version: SMF 2.0 RC3
TP version: TP 1.0 RC1
Theme name and version: Test theme - it's just a copy of the default theme
Browser Name and Version: Firefox 3.6.10
Mods installed: Tinyportal, Subaccounts, ADK Blog
Related Error messages: None that I can find

So, I entered in a few test articles, saw that the panel on the side said I had 3 articles in the submission queue and went in to check them out.  I deleted 3 articles without approving or activating them.  However, that panel still says there are 3 articles awaiting submission.  But when I click on it, there is nothing there.

Any ideas?
Title: Re: Article Submission Queue
Post by: IchBin on October 13, 2010, 08:01:16 PM
You have to go into the smf_tp_articles table in your database and delete the rows for those articles that you are speaking of. Make a backup before you do any changes.
Title: Re: Article Submission Queue
Post by: Gossamer on October 14, 2010, 05:44:07 AM
Alright, thanks.  I'll try that.  Is this something that will happen every time I delete an unapproved article then?

Edit: Unfortunately, that didn't work.  I deleted the extra rows for the articles and now my database only shows the 3 articles I currently want to keep.  But the queue still says there 7 articles in it.

I'm new to databases and smf.  Is there some kind of wait time before it takes effect?
Title: Re: Article Submission Queue
Post by: ZarPrime on October 14, 2010, 04:47:42 PM
Gossamer,

Just a guess here since Ichbin knows more about this than I do but try clearing your browser cache, closing the site tab, and then opening it again and see if that clears it.

ZarPrime
Title: Re: Article Submission Queue
Post by: IchBin on October 14, 2010, 05:47:14 PM
To be honest I didn't know what I had done at the time. And the fact that you saw your problem right away made me think it was the same problem. It could still be, I just don't remember every detail of what I looked at when I fixed this problem. It could very well be that this is a bug. I'll have to test when I get a chance.