a lot of warnings in Plans area of CBsubs 4RC2

I see about 20 lines of this warning when I lick on Plans
Warning: Parameter 1 to cbpaidPlansMgr::productObjects() expected to be a reference, value given in /home/ocularnu/public_html/libraries/CBLib/CBLib/AhaWow/View/RegistryEditView.php on line 4262

Page loads ok though

ThePiston wrote: I see about 20 lines of this warning when I lick on Plans
Warning: Parameter 1 to cbpaidPlansMgr::productObjects() expected to be a reference, value given in <span>/</span>home<span>/</span>ocularnu/public_html/libraries/CBLib/CBLib/AhaWow/View/RegistryEditView.php on line 4262

Page loads ok though

Have you installed the latest CBSubs 4.0 RC2 nigtly and did you upgrade everything CBSubs related you already had installed?

cbsubsbot also?
cbsubs module?
all cbsubs plugins?

not nightly build no, but I do not think this error is causing any issues actually. I forgot for a moment this is RC.

ThePiston wrote: not nightly build no, but I do not think this error is causing any issues actually. I forgot for a moment this is RC.

Try and install nightly build of CBSubs 4,0 RC2 from here:

www.joomlapolis.com/downloads/doc_details/671-cbsubs-gpl-nightly-build

It is closer to stable than RC2 is.

And make sure you upgrade all relevant CBSubs sub-packages.

This seems to be an issue with the 2.0.8 update running CBSubs 4.0.0-rc.2. On a fresh install with 2.0.8 I noticed this same error would repeat itself the more plans I had. I also noticed I could not copy or delete plans and the 'Price per period' and 'Price first period' columns displayed a failure message rather than the proper values.

I also tried the nightly build of 2.0.8 and it didn't fix any issues. Personally I wouldn't suggest running the nightly build on a live site, as noted in the description.

I tried installing a fresh install with 2.0.7, which is the latest update you can use with CBSubs 4.0.0-rc.2, as I have been using on a live site, and everything works fine.

If you're running a live site I suggest rolling back to 2.0.7 and cloning your site to a mockup subdomain with a separate database for testing any updates.

Hope this helps.

I installed 2.0.9, and the problem is still there.

Installed 2.0.7, and (as codesigns said), the problem went away.