CiviCRM Community Forums (archive)

Joomla 2.5.8 (upgraded from 1.7x)
CiviCRM 4.2.6 (upgraded from 4.0x)

Situation is this - client needed a specific format for the Renewal Reminder Letter template. Our coder created custom hooks to insert in the letter.

If you choose the template and use it for a one-off email, it fires of fine and fills in the information as appropriate.

The original date to send renewal reminders was 30 days prior to the end dated of the fixed membership period.

I ran the job to set renewal reminders - that was successful.

Now I can't figure out which scheduled job to run to actually send the reminder letters now that it's past the reminder date.

I get a smarty error when I run process_membership, which is what I understood to be the job that sends out the renewal reminders.

Thanks in advance for shoving me in the right direction.

We needed to create tokens to insert membership data that was already in the database plus doing calculations to 'advance' membership types based on criteria.  Tokens created were:

Current year + 1
membership type (based on number of years as a member of the Bar)
membership price (based on type, above)

Yes, I am aware that the reminders have changed between the two versions and I have set up recurring reminders once the initial has gone out. Do you recommend that I remove the reminders 'clause' in the Membership Type and rely solely on the scheduled reminders feature. If so, would I need to create one reminder to get the initial renewals to fire off, regardless of Renewal Reminder Date? After the initial letters have gone out, I guess I would just reset the Initial Reminder to 30 days before end date?

Because we didn't have a renewal reminder letter ready, memberships had not been populated with a reminder date, so I ran the scheduled-job to resolve that.

I had tried to run the process_membership job to send out the letters (by 'force') but that related in a smarty error.

Thank you for responding!

Thanks Michael -

I did remove the 'old' reminder settings in the memberships and they are set up with the new system. When I run the scheduled reminder job manually, I still get the smarty error. I found another thread regarding this sort of thing and AJ is helping me there, too.

I will definitely look over the scheduled reminders doc to see if I can suggest edits/clarifications.

I'm tweaking a few other things on this end and will see if things run successfully (or not!). 

I'll report back.

That's really interesting...I don't use a token for membership end date, as all memberships expire at the end of the year. Unfortunately need to keep membership type as that gets calculated and memberships are advanced depending on the result of that calculation.

So, my guess is that the culprit is membership.type.

Have either of you posted the actual 'smarty error(s)' that you're seeing? I'm not finding them on this thread.

Arghh - that error is not really helpful. Not sure if the '[in string' actually means the problem is related to an unexpected open bracket ??

By any chance do any of your membership type titles have brackets?