Moderation does not seem to work properly ?|?|?

Reply

BuddhikedeSilva Posted: Wed, Jul 19 2006 7:38 PM

rated by 0 users

Guys,

We are running our blogs in a CS 1.1 instance. Currently we are facing two problems.

1.       When we enable comments moderation they are not displayed until they are approved. However, we are not getting the email notifications when the moderation is turned on. After stepping through CS sources we figured that the email notifications are sent only for the approved comments… Is there a way to get email notifications for the pending ones?

2.       When we try to approve comments from the manage feedback page in the admin area, we get a null reference error. Actually this error is what exactly described here http://communityserver.org/forums/thread/491827.aspx. While playing around it we figured that Emails.SectionTracking method fails because post.User property accessed in the following condition statement returns null. is null (please see the last few lines of this method body).

foreach (string email in threadSubscribers.Keys)

{

   User subscriber = threadSubscribers[email] as User;

   // Make sure we don't send an email to the user that posted the message

   //            

   if (subscriber.Email != post.User.Email)

   {

      EnqueuEmail(epm(post,subscriber,formats));

    }

}

Is there a fix available for this?

Finally, we have currently setup another instance of CS for debugging. But this instance also points to our production database. In order to start debugging we had to add our debugging url to the database by running cs_system_AddNewUrl stored procedure. So would it cause problems in our production version if we leave the entries added by this command in the database? And of course, If “Yes”, how can we rollback the changes?

Thank you very much in advance!

Cheers,

Reply

Scott Watermasysk replied on Thu, Jul 20 2006 10:54 AM

rated by 0 users

THere is no way of getting around the comment moderation issue in CS 1.1. This was a new "feature" of CS 2.0 and much improved in CS 2.1.

There is no published fix for the exception you mention except for using CS 2.0. All the code for blogs is published as part of the SDK, but to be honest, it maybe much easier to just upgrade to a more recent version.

As for the debugging URL, that should not matter. You can manually delete the records from both the cs_Sites and cs_SiteMappings table if you want.

HTH,
Scott