mogmismo

I’m loving the direction of this. We’ve tried to use assignment desk (now defunct) w/ edit-flow to get this feature set, but it never worked right.

A bonus feature that I would really like to see is for each thing in the pool to have the ability to be claimed (dibs) by a certain number of people from each role. So the story takes 1 photographer, 1 reporter and 1 editor, all three can claim dibs on it, then it becomes a post.

On the 1969 issue, yes, 0.7.1 seems to fix the problem, for users that are created after the upgrade. Users created prior to 0.7.1 still have the wrong date the first time they visit the calendar. Not a big deal though, unless you have a huge amount of staff that you are trying to get on-board w/ editflow. Thanks for the bug fix!

I’ll second that, $all_usergroups is empty when called directly, as phracktale is calling it.

I’m trying this to list the groups on a frontend contributor template, such as:

John Doe is a photographer, editor and writer for our site.

I’d like a way, from frontend templates, to get, as an array, the groups that a user is in. Kind of like the iterater in coauthors plus, if possible. I’ve verified that I’m sending the user’s ID (as a number) to get_usersgroups_for_user(), but $all_usergroups (in line 1040ish) is var_dumping as:

array(2) { [0]=> bool(false) [1]=> bool(false) }

thanks,

M.

I can also confirm this, works on 3.3x, but not 3.2.1.

Not only emails, but comments on peoples blogs, too:

Google search for “My name is Dave and I work for a small startup that makes WordPress

We all write plugins, but we don’t shove ads everywhere on the web. I’d reconsider your business practices, nrelate.

M.

I’ve written a blog howto on accomplishing this, but my technique requires editing the plugin’s javascript file (audioplayer.js), so it kind of locks out auto update on this plugin.

Adding Google Analytics to “Wordpress AudioPlayer”

It would be a great feature to have in the core.

Hmmm… Had to apply the same fix on 2.4 as w/ 2.1.4.

Any ideas? Other plugins handle switching between http and https Ok.

Thanks,

-Mog

The only huge drawback to MailPress is no bounce management. I can’t justify using the plugin until there is some method of handling bounces and removing dead users from the mailpress DB. (A counter threashhold system, where they are dumped after X # of bounces)

Thanks,

-Mog

I’ve upgraded the plugin to see if https is fixed, but alas not. Code for the new plugin version had to be changed again, but different this time:

if ( file_exists($this->p_dirs['path'] . 'style.css') ) {
                                        //$url = $this->p_dirs['url'] . 'style.css';
                                        $url =  '/wp-content/plugins/sideposts/style.css?ver=2.1.4';
                                }

Any chance of having final function _enqueueStyles() be smart about if http/https is used?

Thanks,

-Mog

I’m having the same thing going on (2.7.1). I too have the

“Comment author must have a previously approved comment”

checked, but they go into moderation frequently (and randomly).

I have the following plugins installed that influence comments:

defensio
ajaxed wordpress (for better comment threading)

I’ve got no blacklisted words, I’ve checked that both the email and name are identical in the previous posts and the new held posts, and the comments do not have links (or are under my link threshold)

Any ideas?

The audio player 2.0 plugin is great, but it would be nice if the javascript additions to the header could figure out if it were called via https:// or https:// and link appropriately. Otherwise, people get a “Secure and Insecure items” error on load in https:// SSL mode.

Thanks!

Yes, this is a needed feature!

Keep up the good work.

Boy, I second that. Having an author loop would be great. Care to share your wp_list_authors_with_avatar ?

Just found the hook: pre_comment_approved I think that’s what I need, yes?

Ok, I spent all morning making a manual patch to comment.php in wp-admin to send out an email, but it would never fire. Found out the case “approvecomment” in there never fires, but the dim-content case in admin-ajax does. That took way too long!

So, I added a @wp_mail() function in the correct part of dim-content and it works. ~BUT~ it’s dirty and not upgrade safe. What’s the correct way to add this functionality?

Thanks again.