By franfaulkner on Saturday, 16 December 2023
Replies 12
Likes 0
Views 585
Votes 0
I have entered various new events into JEvents this wekk, and although they show on my Joomla website, they are not syncing across to Google Calendar. I have tried deleting the Google Calendar and re-exporting, but only events created prior to 13th December 2023 are showing in it.
Can you give me the URL of your calendar that Google is using to import the events then I can check if its content makes sense
·
11 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
Downloading the calendar file as an ICal I see this

Screenshot from 2024-01-02 15-37-46.png


I don't think this is being generated by JEvents as we don't use this in our existing codebase.

Try setting error reporting to none in the Joomla config
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
I have had an email from one of my users reporting not being able to edit any events in the frontend. He says

There is a problem with the web site when I try to make change on the calendar and save it I get the following message:

parsererror, SyntaxError: Unexpected non-whitespace character after JSON at position 99 (line 1 column 100)

I cancelled my change and tried opening up the existing event again to edit and then tried saving it without actually making any changes and it still showed the same error, suggesting that the problem was already there.

As a test I also could not save an unchanged event .... I suspect that a non-legal control/formatting character was uploaded to the 2024 calendar.


Could this be related, and if so how might we fix it?

btw Errror reporting was already set to none.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
These problems are all related I expect.

See this partial screenshot from your home page

Screenshot from 2024-01-03 10-50-34.png


This error is probably appearing in all your page requests - probably from system plugin or your template.

I see you only have one template on your server (quite old from what I can see) - can you install another template to confirm that this is where the problem arises.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
I will try another template and let you know how I get on.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
Remember to disable the system plugin that comes with your current template when you do the testing.

Your site is quite simple - you should be able to replicate it quite easily with one of the core Joomla templates? May be a good time to move to Joomla 4 at the same time.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm probably being obtuse, but cannot find the core Joomla templates.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Geraint

I found the core templates!
I decided to follow your advice and go for Joomla 4.
Do I need to uninstall JEvents to upgrade from Joomla 3.10 to Joomla 4? I keep getting the following error after running the upgrade.

joomla upgrade crash screenshot.png
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
That is a plugin that doesn't work in Joomla 4

Did you upgrade everything first and check the compatibility tables before upgrading?

If you manually edit the configuration.php file you can set $debug = 1 and then you will see where the problem arises
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
p.s. If you can give me FTP credentials and login details for your site I can get it back up and running for you - then you can remove/upgrade the items that you need to repair.
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
I did the upgrade on a staging site, so still have the old 3.10 site running now. I eventually removed every plugin and was able to migrate, but now have issues with JEvents in the Joomla 4 site. There are also issues with not being able to edit certain types of module, which I guess I will ask about on the Joomla migration forum. I posted a fresh query here:- https://www.jevents.net/discussions/missing-events-missing-categories-after-migration-from-joomla-3-10-12-to-joomla-4-4-1
·
10 months ago
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post