Can you update the following site details at https://stackideas.com/dashboard/site so we can better have a check?

1. Joomla backend login credentials

2. FTP access login credentials

3. Database access login credentials

I think I found the issue, can you execute the following SQL query from your database and see how it goes?

DELETE FROM `#__easyblog_composer_blocks` WHERE `element` = 'note';

Replace #__ to your table prefix before executing it.

Also, may I know how did you perform this update just now?

I have the same problem, I just updated easyblog to a new version and it reports the same message. How to fix it?

Quoted from Pavel Kocian on Tuesday, 01 March 2022

I have the same problem, I just updated easyblog to a new version and it reports the same message. How to fix it?

It seems like this issue only occurred when you update via single-click updater.

For now, you can follow my previous reply instruction on how to execute the SQL query from your database.

https://stackideas.com/forums/error-message-call-to-a-member-function-meta-on-null#reply-570319

Same error here after upgrading, the sql query you adviced didn't fix the problem

FIX
Head to your EB Dashboard and download Launcher Pack. Upload it to your website and proceed with the installation. Now everything works as it should.

I am sorry for the inconvenience.

Just an update, we already applied a temporary fix on our server, so whoever updates to the latest version of Easyblog via single click update, should work fine now.

If you already updated Easyblog to 6.0.3 earlier then you probably will hit this error Call to a member function meta() on null so you can manually copy the following SQL query, execute this from your database.

DELETE FROM `#__easyblog_composer_blocks` WHERE `element` = 'note';

Replace #__ to your table prefix before executing it.

But if the issue still persists, you can start a new thread on our forum, our moderator will help you investigate this issue.

Hello, we have the same problem but I don't know where to search for what you wrote:
As always I used the "update now" function for all updates that were there...

Quoted from Arlex Wong on Tuesday, 01 March 2022

I think I found the issue, can you execute the following SQL query from your database and see how it goes?

DELETE FROM `#__easyblog_composer_blocks` WHERE `element` = 'note';

Replace #__ to your table prefix before executing it.

Also, may I know how did you perform this update just now?

Hey Joshua,

You can check your current database table prefix from the backend global configuration page. (screenshot: https://monosnap.com/file/dcwUWYGL003oiIY57IcHfDgu8AGgKe

If you are still unable to make it work, perhaps you can start a new thread on our forum and provide us with your site backend and FTP access so we can help you now.

I had this issue and got resolved by Arlex promptly 💪🏼

Perform the following:
delete from `#__easyblog_composer_blocks` where `element` in ("note", "liveleak", "livestream", "modules", "mtv");

Replace #__ to your table prefix before executing it.

Thanks for sharing Amritpal Singh

Just for your information, I have locked and marked this thread as resolved to avoid confusion in the future. Please start a new thread if you have any other issues in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.