Thread

Hi,

my EE installation runs for allmost 3 years now - without problems. Recently I use v1.6.3. A few days ago, I installed MSM and yesterday I successfully duplicated my weblog to a new development site with Dereks help.

Now I noticed that I can’t comment anymore. EE says, that I wouldn’t have the permission.

This problem occours on my existing blog as well as on my duplicated blog on the new development site. I’ve never changed the default permissions and users normaly dont have to be members to comment in my blogs.

Does anyone know what to do?

Update:
Seems, that with MSM & Site creation my admin account is damaged. I even can’t log out from the CP. When I clear all caches and don’t open CP, I can write comments. If go to the CP, I can’t.

Do you have access to the database?  And- you can login to the cp ok- make changes there- but if you’re logged in backend, can’t add comments on the frontend?  What’s the exact message you get when you try?  If you quote it, I can search out the triggers in the code.

Also- if you check the db- for your record in exp_members, what’s the group_id?

Hi Robin,

after clearing cache & cookies, I finally could log out.

Do you have access to the database?

Yes, of course. All my sites are running ...
If you mean, phpMyAdmin, then again: yes, i have access.

and- you can login to the cp ok- make changes there- but if you’re logged in backend, can’t add comments on the frontend?

Exactly. I can login/logout (tested also with an alternative super admin login), can make changes to comments and blogentries .... but can’t comment in the front end.

What’s the exact message you get when you try?

With captchas (de)activated:
Error: Unable to receive your comment at this time.

Also- if you check the db- for your record in exp_members, what’s the group_id?

Group-ID is 1 for both of my accounts

I hope, that helps. It’s really stange

Ah- are you maybe trying to do a test comment?  I think that’s the error for a duplicate comment.  I’ve run into it doing ‘this is a test’ multiple times.  Sound possible?

Hi Robin,

Ah- are you maybe trying to do a test comment? I think that’s the error for a duplicate comment.

Yes, I try to do commenting tests. For that I set time span for duplicate comments down from 120 to 10 seconds. But I still get this error message, even for the first comment after a long time.

Hm- there may be more oddness going on.  But let’s see if the setting affects things- go to ‘Admin- System Prefs- Security’ and flip off ‘Deny Duplicate Data?’.  Let’s just see what happens and go from there.

But let’s see if the setting affects things- go to ‘Admin- System Prefs- Security’ and flip off ‘Deny Duplicate Data?’.  Let’s just see what happens and go from there.

After flipp ‘Deny Duplicate Data?’, there changes nothing.

But when I remove the time span (leave the input field empty) from the comment settings of the blog, then my comments are accepted.

Hm- let’s see- the only place I spot that exact message is in:

/** ----------------------------------------
        /**  Do we allow duplicate data?
        /** ----------------------------------------*/

        if ($PREFS->ini('deny_duplicate_data') == 'y')
        {
            if ($SESS->userdata['group_id'] != 1)        
            {            
                $result = $DB->query("SELECT COUNT(*) AS count FROM exp_comments WHERE comment = '".$DB->escape_str($_POST['comment'])."' ");
            
                if ($result->row['count'] > 0)
                {                    
                    return $OUT->show_user_error('submission', $LANG->line('cmt_duplicate_comment_warning'));
                }
            }
        }

Shouldn’t be checking at all if you’re being seen as a superadmin.  So something seems goofy there. 
Changing the time span likely means the db was cleared out.  And setting deny to ‘n’ also means it shouldn’t be triggered- so more goofiness.  AND- the comment timelock shouldn’t have an effect on that message- and if triggered, the message should be ‘You are only allowed to post comments every %s seconds.’  Which- should also not apply to superadmins:

/**  Is there a comment timelock?
        /** ----------------------------------------*/

        if ($query->row['comment_timelock'] != '' AND $query->row['comment_timelock'] > 0)
        {
            if ($SESS->userdata['group_id'] != 1)        
            {

Hm- you up for doing a quick upgrade to 1.6.4.  I’d like to blow the dust out, make sure nothing’s odd or changed.  Also- double check your cookie domain - think you’ve got another thread on that one- and it may related to why this is affecting you at all as a superadmin.  And lastly- make sure the settings you are flipping are for the MSM site you are on- they’re site specific and some are site and weblog specific.  But in general, the results aren’t making a ton of sense based on a look at the code.  So- an update might eliminate gremlins.

Update to 1.6.4 ... nothing changes.

Also- double check your cookie domain - think you’ve got another thread on that one- and it may related to why this is affecting you at all as a superadmin.

That’s the only thing, I can’t change. As I have multiple blogs (2) on two domains, the cookie domain can’t fit both. That’s why I bought MSM to get a clean solution in the future.

If it helps, I can give you an account for my site/database via PM/Email. Then you can take a deeper look.

If you don’t mind- yep, that would be helpfull.  I just don’t get why the changes you made result in the outcomes you’re getting.

Hm- go ahead and pm over the url to the backend, username and password.