Read more location text in a plan

What might work is since you have a content plugin that creates the readmore link, why not have it run a query to pull the read more text during that same DB query? The in the plan definition, you could type in what you want for readmore text.

This is one of those sites where you have a base free plan, and a paid content plan and its very hard to put in a readmore (simple one) that covers both bases. Readers are simple and easy to confuse. Most of the people that use this site are doctors world wide.

The problem isn't getting data to it the problem is you can have an unlimited number of plans protecting the article. So which do you display? First one? Last one? All of them? None? Really the only solution is a generic string. Providing a plan name shouldn't relieve any confusion though. I suggest changing the string to be very clear they need a subscription to continue reading (when they click it'll show which plan or plans allow access) that best fits your userbase.

Gotcha.. we have 1 plan protecting one set of categories and another protecting the rest. What you referring to is when they click the link, it takes them to a generic subscription page with all the plans.

The only way I could think to get around that is if CBSubs content plugin queried the plan protecting that content category?

WebJIVE wrote: Gotcha.. we have 1 plan protecting one set of categories and another protecting the rest. What you referring to is when they click the link, it takes them to a generic subscription page with all the plans.

The only way I could think to get around that is if CBSubs content plugin queried the plan protecting that content category?

Chiming in here ... I believe the issue with such a feature is what should be done if the same content is protected by multiple plans.

Your case is simple (protecting content with only one plan) but most use cases have multiple plans protecting the same content.

Agreed.. When I sit back and think about the other ways to configure this, it could be done but, at what cost to fattening up CBSubs core.

On that subject, when/if are you guys going to drop support for Joomla/Mambo 1.0 and Joomla 1.5? It seems as though feature and release cycles would speed up if you guys didn't have to deal with all that legacy code.

WebJIVE wrote: Agreed.. When I sit back and think about the other ways to configure this, it could be done but, at what cost to fattening up CBSubs core.

I also do not see a clear feature request specification here.

On that subject, when/if are you guys going to drop support for Joomla/Mambo 1.0 and Joomla 1.5? It seems as though feature and release cycles would speed up if you guys didn't have to deal with all that legacy code.

At this point it does not cost us any development effort really.

Most effort is consumed trying to work-around new Joomla bugs.