[SOLVED] Different hours in the backend and CBSubs

the documentation says:

"By selecting this parameter the system will construct a URL that can be
used to schedule a Cron job to periodically trigger mass expiration
queries. You will also be prompted to specify the maximum number of
subscriptions to expire per cron task as illustrated in Figure 47."

I am not english, I try to do what I can to understand. I'am so sorry. I think I must clik on the link to configure the timing of the cron job.

So I do not understand what option to choose if I want the expiration to be automatic in the backend event if the users is not connected.

Can you help me please.

myann wrote: the documentation says:

"By selecting this parameter the system will construct a URL that can be
used to schedule a Cron job to periodically trigger mass expiration
queries. You will also be prompted to specify the maximum number of
subscriptions to expire per cron task as illustrated in Figure 47."

I am not english, I try to do what I can to understand. I'am so sorry. I think I must clik on the link to configure the timing of the cron job.

So I do not understand what option to choose if I want the expiration to be automatic in the backend event if the users is not connected.

Can you help me please.

A CRON job is a service that is typically provided by your host.
It is basically a scheduler that is programmed to execute a specific URL at periodic intervals (example every 5 mins).

CBSubs provides the URLs needed to check/expire any subscriptions.

You need to use those URLs to configure your CRON jobs.

Please consult you hosting help-desk for further assistance.

Nant, Thank you so much.

I will look for it ASAP. But my problem of different hours between my backend and CBSubs (or CB) is not solved.

Would you know what happen ??

Backend CBSubs I believe is always UTC (no offset applied), but backend of rest of CB will apply your global offset or your users offset. You can verify this by comparing the displayed datetime to the datetime in your CBSubs database tables (see _cbsubs_subscriptions for example).

Thank you for this.

I think this is something developpers have to think about in the next release.

Don't understand what there is to think about. Can you make a suggestion? How do you want it to display? How did you expect it to display?