By WillockBoy on Monday, 15 May 2017
Replies 15
Likes 0
Views 1.6K
Votes 0
Is it possible to use an existing mysql table with JEvents?

The existing table holds current "diary" events such as date, event, start time, finish date.

With thanks.
geraint

Apologies for not posting more information before now, as I've been doing some testing with EasyCron. Unfortunately, I keep getting an error stating that "Sometimes consecutive failures is due to execution timeout of the cron job. Upgrading your plan will help increase the max timeout limit.".

However, more importantly our server host's Cron job works well.

I'm very impressed with the JEvents connectivity to our gmail calendar and thank you again. We will be purchasing a gold membership shortly.
·
Sunday, 11 June 2017 14:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

I'm afraid not. JEvents needs it's own database and tables for it to function.

You can import events into JEvents though. Please see:
https://www.jevents.net/frequently-asked-questions/importing-events-in-csv-format

Many thanks
Tony
·
Monday, 15 May 2017 21:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Tony

Many thanks for your reply.

I have now discovered that JEvents has the ability to use a live Google Calendar and can refresh the data using a cron job.

I have set up a JEvents calendar to use our Google Calendar and the refresh button works well. However, I am unable to use the recommended code:
/usr/bin/curl -s "http://www.mydomain.com/index.php?option=com_jevents&icsid=3&task=icals.reload"; > /dev/null 2>&1
as my web site host's cron job keeps rejecting the code. Obviously, this makes sense as no one wants the code refreshing by any "Tom, Dick and Harry". I've also added the code to a CRON job and, naturally, get a 303 error.

Having read your forum, I have also tried another solution by adding a PHP file that sends the URL to our web site. However this returns the error that only the Super User has access to the component, which is correct. Can you help, please?

My other problem is getting the Calendar to display "full size" without using the "Switch View" module. How can I accomplish this, as I seem to have tried every option available.

I am very impressed with your component but feel that I need to test the possibilities further before buying a Gold or Silver membership.

With thanks.

Stephen
·
Wednesday, 17 May 2017 12:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Did you enable anonymous refreshing of the calendar when you edited it in JEvents - you need this setting for the cron job to work.

You shouldn't worry too mush about 3rd parties updating your calendar since the data source is google and they can't put any events into your google calendar
·
Monday, 22 May 2017 13:49
·
0 Likes
·
0 Votes
·
0 Comments
·
geraint

Thank you for your reply.

In my list of calendars, there are two. The first is the DEFAULT calendar and the second is the one accessing our Google calendar. This is the calendar where anonymous refreshing has been enabled. This option does not seem possible on the other calendar and I assume that that is quite correct.

I have also listed the super users in the list of authorised used of JEvents. However, the Cron job refuses to work. Our web host is STRATO and their cron job refuses to accept the recommended statement:
/usr/bin/curl -s "http://www.xxx.xxx/index.php?option=com_jevents&icsid=3&task=icals.reload" > /dev/null 2>&1
it simply leaves "/usr/bin/curl " in place and the rest of the field blank as well as suggesting that " > /dev/null 2>&1" is not acceptable. I have tried using it in several ways without success.

I have also tried a free account at EasyCron where the URL alone is requested and that does not work either.

Kind regards.
·
Monday, 22 May 2017 20:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Can you give me the domain on the private site details tab below and I'll take a look
·
Wednesday, 31 May 2017 09:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Geraint

Many thanks for your help.

Access details have been sent, as requested.

Stephen
·
Wednesday, 31 May 2017 14:29
·
0 Likes
·
0 Votes
·
0 Comments
·
sorry for the delay in responding - I've been at the JandBeyond Joomla conference (http://www.jandbeyond.org).

When I access your update URL http://www.mXXXb.co.uk/index.php?option=com_jevents&icsid=3&task=icals.reload I get a "Not Authorised - must be super admin" message

I therefore tried to log in the backend but it says the password is not correct - can you check the credentials please?
·
Monday, 05 June 2017 18:15
·
0 Likes
·
0 Votes
·
0 Comments
·
geraint

Apologies, your account was not registered as a Super User account.

Please try again and thank you in anticipation.


Stephen
·
Monday, 05 June 2017 20:08
·
0 Likes
·
0 Votes
·
0 Comments
·
I can now login to the frontend but I can't access the backend
·
Monday, 05 June 2017 21:37
·
0 Likes
·
0 Votes
·
0 Comments
·
geraint

I've now disabled Two Factor verification on the account and changed the password (Private Site Details completed).

Sorry to be such a nuisance.

Stephen
·
Monday, 05 June 2017 21:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Havng logged in I see that the autoreload URL is actually http://www.mXXXb.co.uk/index.php?option=com_jevents&icsid=5&task=icals.reload - notice the 5 and not 3 a you had earlier

When I load this in a webbrowser it refreshes the calendar correctly. This URL should work at an online service like EasyCron or via your webhost.

If you can't get it to work with your webhost then I suggest you ask them for advice for that the correct format should be for their set up
·
Tuesday, 06 June 2017 07:45
·
0 Likes
·
0 Votes
·
0 Comments
·
geraint

I am very grateful for your time and help.

Stephen
·
Tuesday, 06 June 2017 09:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Does this mean you got it to work in your cron job?
·
Sunday, 11 June 2017 11:40
·
0 Likes
·
0 Votes
·
0 Comments
·
It sounds like it maybe your host is limiting remote access run times. Opposed to local crons :-)

Glad you have it all working and hope to see you in the Gold forums soon!

Many thanks
Tony
·
Sunday, 11 June 2017 23:51
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post