Ah, I see. I've confused 2 issues. That appears to be a separate issue entirely and have added to an existing bug ticket for Beat to review possible cause. From what I can tell its been fixed internally for next release already however.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
May I ask how this error was avoided? I've recently upgraded CB to 1.7.1, CB Subs to 1.2.2, and CB Conditional to 1.3.0. I'm not using Plan Image...it is installed, but unpublished.
Again, how may I avoid this error:
Warning: preg_match() expects parameter 1 to be string, array given in <span>/</span>home<span>/</span>.../public_html/components/com_comprofiler/plugin/user/plug_cbpaidsubscriptions/cbpaidsubscriptions.condition.php on line 196
I only see this error when I login and view my profile on the site where the above noted software is installed.
EDITED NOTE of CLARIFICATION: ALL users see this error when logged into site. Thought maybe this post was being 'ignored' because it appears as if 1 user, at 1 site is seeing the issue. Again, ALL users of this particular site are seeing the error noted in this post on their profile page.
Best regards...
J
Last edit: 13 years 3 months ago by jsrunder. Reason: Clarification of "I" vs "ALL USERS" on site.
krileon
