Header issue on frontend (fatal error)

Hi there,

I’m very excited about the new features! Unfortunately right now i’m seeing a fatal error on the frontend of my site: Fatal error : Cannot declare class Cornerstone_Header, because the name is already in use in /public_html/wp-content/themes/pro/cornerstone/includes/classes/regions/class-header.php on line 3

I’ve tried disabling any plugins and customizations but the error persists. In Pro, no Headers are shown in the Header tab (just “Uh oh!”).

Is there any info I could provide for debugging purposes?

Same problem here, turned off all plugins… no difference. Switched themes, and the site loaded ok. Using Siteground, so php memory is 700+. Latest Wordpress version. At top of backend dashboard it says: “…eedle in /home/englishs/public_html/familysprout.com/wp-content/themes/pro/cornerstone/includes/classes/admin/class-status.php on line 436 …” Not what the whole text says as it is covered by dashboard left side menu bar. Also CSS and Java were deleted to check for interference. No difference. Thanks!

Hey @Frimatek and @Stephenk,

When you installed the beta version, did you install it by dragging the folder over an existing version of the theme? That file was moved, so if the original version wasn’t deleted (happens if you replace existing files) then it could be trying to use an older version of the file.

Yeah, I used Cyberduck and dragged the Beta version file to WPContent>Themes… and selected “Overwrite”

Is there a better way?

I believe it was WordPress 5.5, but you can now simply upload/install the same theme again and it will update it for you instead of informing you it is already installed. A very welcome change, before that I would use a plugin to enable that functionality.

If in the event FTP is the only way, usually I rename the folder to pro-new for example and upload it. Then I move the old version up to wp-content and rename pro-new to pro. Then finally delete the old version. It’s cumbersome, but the safest way because in an instant you’ve fully gone to the next version instead of being in somewhat of an in-between state where the site could look broken during the upload.

1 Like

Awesome, thanks!

You’re welcome!