Help Center

Powered by Minitek FAQ Book
Loading...

Shortcode in an article

CB
caroline bultinckPosted 8 months ago

the system to follow remains pending in my articles

Loading...
0
#3983

22 answers

M
MinitekPosted 8 months agoModerator

I was able to log in successfully.

Notifications events will remain pending until they have been processed.


Processing notification events


The processing of a notification event is done automatically via Scheduled tasks. When a notification event is processed, Updates are created and Emails are added to the email queue. All users that have subscribed to the object (article) of the notification event (or to a parent of that object: category, tag, author) will see the updates in their personalized My Updates page.

Also, Emails will be created and added to the email queue for all users that have selected to receive email notifications for the object (article) of the notification event or for a parent of that object (category, tag, author).


Scheduled tasks


Before setting up the scheduled tasks, you must first go to the component Configuration. Under the tab Scheduled Tasks you will find the option Password. In that box you have to enter a password which will allow your cron jobs to access the required front-end urls. After you're done, click on Save & Close.


  Important

Use only lower and upper-case alphanumeric characters (0-9, a-z, A-Z) in your password.


Now you can set up the actual scheduled tasks (cron jobs) in the hosting control panel. Log in to your hosting control panel and search for a section called Cron jobs, Scheduled tasks or something similar. If you can't find it, ask for help from your hosting provider.


  Warning

If your host only supports entering a URL in the cron jobs, this will most likely not work with Content Notifications. There is no workaround. It is a hard limitation imposed by your host. We would like to help you, but we can't.


Create updates - command line (wget)

wget -O --max-redirect=10000 /dev/null "http://www.yourdomain.com/index.php?option=com_contentnotifications&task=notifications.createUpdates&password=YOUR_PASSWORD"

where YOUR_PASSWORD is the password that you entered previously in the component configuration.


Create email queue - command line (wget)

wget -O --max-redirect=10000 /dev/null "http://www.yourdomain.com/index.php?option=com_contentnotifications&task=notifications.createEmailQueue&password=YOUR_PASSWORD"

where YOUR_PASSWORD is the password that you entered previously in the component configuration.


  Tip

If your host does not support cron jobs then you must either move to another host or use a 3rd party service like webcron.org.


---------------------------------------------------------

Let me know when you have set up the scheduled tasks in your server so that we can then fix some issues with the user interface that I see in the front-end in the page: https://carolinebultinck.be/inschrijfmodule

CB
caroline bultinckPosted 8 months ago

I made the cron jobs (see attachment png-file) and password in the configuration under scheduled tasks

but what about minutes, hours.... I used for every item: *  (is that OK?)

 

 

 

M
MinitekPosted 8 months agoModerator

These asterisks represent the timing, which consists of five fields:

  • minute
  • hour
  • day of month
  • month
  • day of week

Each asterisk represents a field in the cron expression, from left to right: minute, hour, day of month, month, and day of week.

By using * for all fields, you are instructing the cron job to run every minute, every hour, every day of the month, every month, and every day of the week.

To execute the script once every hour, you should use the following cron expression:

0 * * * *

This expression specifies that the script should run at the 0th minute of every hour, while the remaining fields can be set to asterisks (*) to indicate any value. This cron expression will execute the script once per hour, rather than every minute.

CB
caroline bultinckPosted 8 months ago

is done, every hour

 

M
MinitekPosted 8 months agoModerator

Ok, now create a new notification event for the article 'test', so that we can check that the cron jobs work correctly.

If they work correctly, you should see that the Notification event will be processed.

This means that the Updates and the Email Queue will be created.

CB
caroline bultinckPosted 8 months ago

notification events (in dashboard) 2 pending

Follows: 1

no email queue

M
MinitekPosted 8 months agoModerator

The first one (Joomla specialist) has a pending Email queue because nobody is subscribed to that article.

The second one (test) has 1 subscriber. We must wait for the second one to be processed by the cron job. It will be processed once per hour, so we must wait until the cron job executes.

CB
caroline bultinckPosted 8 months ago

OK, i wait about 1 hour. And check again

 

CB
caroline bultinckPosted 8 months ago

hello

No mail, no notification. 

Today i tried again, with a new notification, with the article joomla specialist, but no result

Sorry, but I still don't understand how to use this extension, I'm not a joomla beginner and worked a lot with cron-jobs, extensions, templates, css, scripts. But this extension still doesn't work as it should. Can you configurate this extension for me correctly?

 

thanks for your help

M
MinitekPosted 8 months agoModerator

I see that the notification has been successfully been processed and the email queue has been created.

Now there is one last step to send the emails. You must create one more cron job that will automatically send the email queue for all processed notifications.

You can find the command for this last cron job at https://www.minitek.gr/support/documentation/joomla/content-notifications/sending-emails.

After you have created the cron job, emails will be sent. You can create a cron job that executes once every hour.

CB
caroline bultinckPosted 8 months ago

I created the last cron job once every hour, but no mail was send

No more mails in the queue

 

M
MinitekPosted 8 months agoModerator

It seems that the component will just not work as it should in your website.

I'm sorry for the trouble, I will issue a refund right now.

M
MinitekPosted 8 months agoModerator

The refund has been issued and will be finalized within the next 4 hours.

The amount will be visible back in your account within 1 business day.

CB
caroline bultinckPosted 8 months ago

i started with a whole new (empty) website - webdesign-caroline.online

1 article, i installed the extenion and plugins again and i made 3 cronjobs, on an other hosting (siteground). Now I will wait about 1 hour to check

if you want i make for you a super admin user, so you can check

CB
caroline bultinckPosted 8 months ago

Hello

again no mail was send - can i have support please

 

M
MinitekPosted 8 months agoModerator

I have already refunded the money. I am sorry but the extension should be working with the steps that I have provided in the documentation.

CB
caroline bultinckPosted 8 months ago

hello

I started a new website with no extra template or extension. I used the steps provided in the documentation. And it is still not working, it was not necesessary to refund. I only want support to use this extension.

The hosting was checking the cron jobs, and everything was correct - but no mails and no update confirmation.

A third part also tried to use the extension, the same problem. That is not normal that you sell an extension and it is not working. Just give me some support, and thanks in advance

 

 

CB
caroline bultinckPosted 8 months ago

My hosting checked the cron jobs and he asked me about the following ending of the cronjob

 

> 2023-06-20 12:52:40 (0.00 B/s) - ‘--max-redirect=10000’ saved [0/0] suggest that a file called --max-redirect=10000 is created with no content inside of it.

With that said, you might want to ask the extension developers if such output is expected.

 

Can you give me an answer please, thanks 

CB
caroline bultinckPosted 8 months ago

Hello

This is the respons of the technical support team of het hosting siteground:

Further configuration troubles related to the extensions that you are using (in this case - content-notifications), are considered development issues and should be addressed by the extension developer, because such are not covered by our scope of support

There are no entries throughout our logs about other notification emails related to the execution of the cron-jobs, so nothing server side is blocking such emails - they are simply not send and this is something that the developer of the extension should take care of. You must contact the developers of the extension and ask what settings are required in order for all the necessary notification emails to be send out during a cron-job execution.


If there is anything server side related that we should check, feel free to contact us back at any given time.


M
MinitekPosted 8 months agoModerator

I'm sorry but I will not be able to help further with this.

Unfortunately I will have to discontinue the extension. The main reason is the difficult debugging due to the complicated nature of the component.

Most people do not have issues with the component, but for those who have issues, the debugging is extremely difficult and time consuming.