Jump to content


Welcome to DevFuse Forums


Sign In  Log in with Facebook

Create Account
Welcome to DevFuse Forums, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of DevFuse Forums by signing in or creating an account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.
 
Guest Message by DevFuse

(View All Products)Featured Products

Donation Tracker


Help fund your forum with donations, setup goals and track member donations. Offer rewards for members donating.

Timeslip System


Have your members submit their race times and share with others. Intergrates with our Garage System.

Videos System


Allows your members to submit their own videos for community viewing. Support is included for all the major video sites.

Garage System


Setup a community Garage when members add their own vehicles with images and modifications.

Form Manager


Build your own forms for your members without coding experience. Support included for pm, email and topics.

Collections System


Build a community database of items for your members. Full features custom fields included.

Issue information

  • #000127

  • 4 - High

  • Fixed

  • 3.1.1

  • -


Issue Confirmations

  • Yes (0)No (0)
Photo

Send pm and email groups ips error

Posted by Michael on 30 September 2009 - 12:12 AM

Both FIND_IN_SET( {$r['email_groups']}, member_group_id ) and FIND_IN_SET( {$r['pm_groups']}, member_group_id ) will need the clean perm function added.

I too have this issue.Should i wait for a release or is there a fix for it ?

i want to add that i have the pm function activate and post reporting and disabled email. so when i send a test message, i get a database error see attached

Posted Image


dont know what happened but its working now...


Updating status to: Fixed
Issue fixed in: 3.1.2






0 user(s) are reading this issue

0 members, 0 guests, 0 anonymous users