Skip to main content

Warning: Attempt to read property "post_type" on null in plugins/brizy/admin/blocks/main.php on line 207

Answered
Ahmed badawy
  • Edited

Hello

Today one of our client's site was showing this warning without editing or doing anything!

Warning: Attempt to read property "post_type" on null in /public_html/wp-content/plugins/brizy/admin/blocks/main.php on line 207

Warning: Attempt to read property "ID" on null in /public_html/wp-content/plugins/brizy/admin/blocks/main.php on line 208

 

I checked the debug mode of WordPress in config is disabled

0

Comments

37 comments

Date Votes
  • Ariel H.

    Hi Ahmed,

    Thank you reaching out to us.

    This is something we need to inspect from your WP Admin page. Please add us as an Admin user to your WordPress Dashboard and send the following details to: communitysupport@brizy.io

    Community Post link: https://support.brizy.io/hc/en-us/community/posts/21281497557394
    WordPress Admin URL:
    Username:
    Password:

    Please also provide us access to FTP/cPanel so we will have direct access to your WordPress files.
    FTP Host / cPanel login URL:
    Username:
    Password:

    Please make a full backup of your site as a precaution.

    Best regards,
    Ariel H.

    0
  • Timur Taveev

    Hi

    I have the same problem.

    0
  • Ariel H.

    Hi Timur,

    Thank you for reaching out to us.

    Can you replicate the issue with all other plugins disabled besides Brizy and Brizy Pro?

    If the issue persists, please provide us with temporary access to your WP Admin page so we can take a look. Please add us as an Admin user to your WordPress Dashboard and send the following details to communitysupport@brizy.io.

    Community Post link: https://support.brizy.io/hc/en-us/community/posts/22112971369234
    WordPress Admin URL:
    Username:
    Password:

    Additionally, we will also need temporary access to cPanel/FTP:
    cPanel/FTP host address:
    Username:
    Password:

    Please make a full backup of your site as a precaution.

    Best regards,
    Ariel H.

    0
  • Ariel H.

    Hi Timur and Ahmed,

    We're still waiting for your site credentials so we can further investigate the issue.

    In the meantime, please add the following directives in wp-config.php to hide the warning:

    ini_set('log_errors','On');
    ini_set('display_errors','Off');
    ini_set('error_reporting', E_ALL );
    define('WP_DEBUG', false);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    I am looking forward to your response.

    Best regards,
    Ariel H.

    0
  • Solution Clinic

    I have the same Problem!

    Warning: Attempt to read property "post_type" on null in .../wp-content/plugins/brizy/admin/blocks/main.php on line 207 Warning: Attempt to read property "ID" on null in .../wp-content/plugins/brizy/admin/blocks/main.php on line 208

    Deactivated all plugins, error persists. wp-config.php is changed accordingly.

    I'll send you login informations.

    0
  • Ariel H.

    Hi Leonhard,

    Thank you for providing your site's credentials, we have already escalated this issue to our senior support team. I will get back to you as soon as I have any new updates.

    Best regards,
    Ariel H.

    0
  • Impactamídia Marketing

    Hi, I'm having the same error. It is also causing the background on blocks not to work.

    As I'm the third person on the forum to report this, please consider turning this in for a fix.

    0
  • Ariel H.

    Hi,

    Thank you for reaching out to us.

    This issue has already been escalated to our senior support team. I will get back to you as soon as I receive an update.

    In the meantime, please add the following directives in wp-config.php to hide the warning:

    ini_set('log_errors','On');
    ini_set('display_errors','Off');
    ini_set('error_reporting', E_ALL );
    define('WP_DEBUG', false);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    If you don't have access to update the wp-config.php file, you can also use a plugin to hide error reporting.
    https://wordpress.org/plugins/debug/


    Sorry for the inconvenience.

    Best regards,
    Ariel H.

    0
  • Serge Stauffer

    Hello
    I am in the same boat.

    0
  • Serge Stauffer

    The Debug Plug-In does not work for me. The error messages are still there (also after selecting and deselecting all options). 

    Thank you for your help

    Serge

    0
  • Ariel H.

    Hi Serge,

    Please provide us with temporary access to your WP Admin page so we can take a look. Please add us as an Admin user to your WordPress Dashboard and send the following details to communitysupport@brizy.io.

    Community Post link: https://support.brizy.io/hc/en-us/community/posts/22112971369234
    WordPress Admin URL:
    Username:
    Password:

    Additionally, we will also need temporary access to cPanel/FTP:
    cPanel/FTP host address:
    Username:
    Password:

    As a precaution, we recommend creating a full backup of your site.

    Best regards,
    Ariel H.

    0
  • Noah Sochet

    I'm afraid I'm having the same issue.  I was able to hide the debug text, but I'm curious what the broader fix is?

    0
  • Oleg Babenchuk
    • Edited

    Having the same issue.

    The Live version and the editor become unsynched.
    Saving never completes.
    Restoring only made the problem worse.

     

    Email sent with credentials.

    0
  • Ariel H.

    Hi Noah, 

    Sorry about that, a fix to address this issue should be rolled out soon.

    Best regards,
    Ariel H.

    0
  • Ariel H.

    Hi Oleg,

    Thank you for providing your site credentials.

    Your website is now functioning correctly, and the update button seems to be working properly. Please test it on your end to confirm.

    If you encounter any further issues, feel free to let us know.

    Kind regards,  
    Ariel H.

    0
  • Ariel H.

    Hi Serge,

    Thank you for your cooperation.

    We have added the above directives in the wp-config.php file to hide the warnings.

    If you have any further questions, please let us know.

    Best regards,
    Ariel H.

    0
  • Serge Stauffer

    Hello Ariel

    Thank you for your quick help.

    Is this meant as a temporary fix until there is an update of the Brizy-plugin?
    My websites proportions are off now, which is ok, if this is only temporary.

    Best regards 

    Serge

     

    0
  • Ariel H.

    Hi Serge,

    Thank you for the update.

    Hiding the warning is a temporary fix. Regarding the proportions on your website, could you share more details about what you expect for this page?

    Best regards,  
    Ariel H.

    0
  • Serge Stauffer

    Hello Ariel 

    I should have looked in the editor. Now it is clear, the margin of the main block was set at 75px. Now everything is all right, which is great.

    Will this be fixed with the next update? So when this is released, will I just have to replace the wp-config.php with the backup (I have made before installing the Debug plugin)? 

    Best regards

    Serge

     

     

    0
  • Oleg Babenchuk

    Hi Ariel,

    It worked for a few moments, but after saving a few changes, the button started spinning again.

    After a while, it says I have to refresh the page. When the page refreshes the changes are gone and I have to start again.

    Can you please re-check. It seems there is still something wrong.

    0
  • Ariel H.

    Hi Serge,

    I’m glad to hear you were able to resolve the issue. About the warning showing on the front end, it’s a temporary fix for now. Unfortunately, I don’t have a specific date for when the patch will be rolled out, but we will keep you updated on this support thread.

    You can keep these directives in the wp-config.php file, and they shouldn’t affect your site; they will simply hide any PHP errors:

    ini_set('log_errors','On');
    ini_set('display_errors','Off');
    ini_set('error_reporting', E_ALL );
    define('WP_DEBUG', false);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    If you prefer to remove them, just delete the above directives and change it to:

    define('WP_DEBUG', false);

    We’re glad to help you revert it back if needed.

    Best regards,
    Ariel H.

    0
  • Ariel H.

    Hi Oleg,

    Thank you for the update. I checked your site again today, but I couldn’t replicate the issue. Could you please create a short screencast to demonstrate the issue?

    In the meantime, please try clearing your browser cache or editing your pages using a different browser to see if that makes any difference.

    Kind regards,  
    Ariel H.

    0
  • Devcode Srl

    Hi,

    We fixed this issue with this pull request: https://github.com/ThemeFuse/Brizy/pull/2017

    it seems to be a php8.0 related issue.

    Let me know if this will solve your problem.

    Valentina

    Technical support - OpenSTAManager

    0
  • Ariel H.

    Hi Valentina,

    Thank you for sharing your solution. Our team will review it, and we will incorporate the fix in the upcoming updates.

    Best regards,  
    Ariel H.

    0
  • Oleg Babenchuk
    • Edited

     

    It seems to happen when making significant changes or editing more than one element.

    Re-saving Global element Display Conditions seems to help in some situations.

    This makes the editor unreliable; changes beyond a minor adjustment get lost. 

    I have not been able to work on this website despite purchasing Pro only a few days ago. It takes 24 hours just to get a comment approved here and a response. When I first tried this builder, it was very reliable and stable; this was my primary reason for choosing it to begin with. I could have rebuilt the website in a different builder by now. This is really unacceptable. This needs to be fixed immediately, and my subscription discounted or refunded.

    0
  • Ariel H.

    Hi Oleg,

    Thank you for the update. It seems there may be an intermittent conflict with one of your installed plugins. Disabling all plugins except Brizy and Brizy Pro resolves the issue, as shown here: https://youtu.be/khjvYWYD-64.

    I temporarily disabled the currently active plugins but found no direct conflicts, so it appears that one of the active plugins may be causing this intermittent issue. I recommend disabling third-party plugins or enabling only essential ones while working on your website to prevent this issue. You can re-enable them all once you’ve finished updating your pages.

    Kind regards,  
    Ariel H.

    0
  • Oleg Babenchuk

    I can confirm that even upon deactivating ALL plugins except Brizy and Brizy Pro. The issue remains.

    Here is a video: https://youtu.be/eB1CfmRI-1M

    1
  • Ahmed badawy

    @Oleg Babenchuk I have the same exact problem and I did disable all other plugins and still getting this error.

     

    0
  • Ariel H.

    Hi Oleg and Ahmed,

    Thank you for the update. I revisited this today and as shown in the screencast, I was able to make changes to a page with only Brizy and Brizy Pro enabled. You can view the screencast here: https://youtu.be/STPj-VO5XMo

    Could you please try replicating the issue again, either in incognito mode or by using a different browser, and let me know if there’s any change?

    Best regards,  
    Ariel H.

    0
  • Sue Dwyer

    I have the same error and have tried all these fixes except I don't have access to the Cpanel. I sent an email to support 2 days ago.

     

    Regards Sue

    0

Post is closed for comments.

Didn't find what you were looking for?

Ask a Question