When clicking the "Trust" button for blog_id = 7, the application inserts a row into the mt_permission table placing the test " 'comment' " into the permission_permissions field and the value of 0 in the permission_blog_id field. I would think that the blog_id would match the value of the current blog_id? Can someone help me understand this behavior?
Reported on Movable Type 4.3
That blog id 0 means it is trusted at the system level, meaning for all the blogs within you installation.
----------------------------------
Mihai Bocsaru
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
That's what I understood by reading the documentation, but I was pressing the Trust button for a specific blog not the system. I would expect to see text added into the permission record that existed for blog_id 7 not adding a record for blog_id 0? It seems to me like it's a bug, but I don't know enough about the intent of the developers to make that statement.
If you feel it is a bug, you may like to file a bug report from: http://bugs.movabletype.org/
I would rather think it was done in purpose, to be unique at the system level (applicable for all the blogs within the installation).
I was hoping that someone (developer if possible) would say something to the affect that "oh yeah, that's normal behavior and here is why". I thought the trust button applied to a specific blog not the entire system when clicking it from within the blog that I am managing. I don't want to file a bug if it isn't a bug. I think a developer can better say whether they think it is a bug or not.
I'm a long time developer and for me it makes sense to have the "trusting" process applicable at the system level.
On the other hand, if you believe you would have any advantage on "trusting" somebody only at a specific blog level, you may like to request this as a feature.
There will be no harm to be able to trust somebody either at the system or at the blog level.
I would say there will have to be a way to choose if to "trust" at the current blog level or the system level, (in my opinion the default option should be "system level") so that a system admin managing an installation with say a few tens of blogs won't have to go through the "trusting" process a few tens of times (once for each and every blog)...
Mihai,
Thank you for your comments. Did you actually develop the changes from the version (4.01) to the 4.32 version that altered the behavior? The reason this was noticed was that there were almost 500 trusted commenters and when the upgrade occurred the behavior was different and none of the 500 commenters were considered trusted anymore. When I dug into the matter, that is when I discovered what is documented above. Thanks again for your feedback.
Regards,
Jim Barker