-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wp2Static 7.2 Plugin could not be activated because it triggered a fatal error. #914
Comments
Unfortunately, I'm not involved in the plugin since its acquisition and then later being fired. I've reached out to Elementor and offered my consulting to get things updated. We'll see if they're interested. |
@edudemy I got this error when I tried to install the zip from releases as the plugin. After compiling from source code, the plugin worked as expected. |
@leonstafford How does an open-source plugin get acquired anyway? Can't it just be forked and fixed? |
Can you upload that version which works completely fine? I have downloaded from their site and i am unable to active it. |
Do you have any tips on compiling from source? Since Elementor seems to have taken over the wp2static.com domain, none of the useful links (including compiling from source) seem to work any more. Thanks UPDATE: Found info here on how to compile from source. https://craftweeks.com/en/compile-wp2static-from-source-for-static-wordpress-sites/ |
I built this from source and it installs/runs on WordPress 6.6.2 without any apparent error. (plugin .zip file attached). BUT and it's a very large BUT - as the essential Add Ons, for things like Netlify were hosted beneath the wp2static.com domain that Elementor seems to have taken in-house and redirected it to ads for their hosting products, it no longer seems possible to install the essential any Add Ons into WP2Static . Which sadly for me makes it unusable - I used to deploy to Netlify via an Add On. I still have the Netlify Add On installed on a separate site but have no clue where in the filesystem to find it or whether it would be possible to move it over to my new Wp2Static install. UPDATE: Please see my followup post regarding the addon |
My findings. The attached wp2static and wp2static-addon-netlify seem to work without error on the current 6.6.2 WordPress. Deploying to Netlify via the addon also completes without error. However for reasons I don't understand, some of my deployed content URLs (images, header items and some css) seem to want to prepend "https://example.com" where there should be https://mysite.netlify.app. These items show up fine on the local version of the site (For test purposes I'm running it in LocalWP on Mac) I can see no reason for this but if anyone else has any ideas I'll gladly give it a try. UPDATE: Entirely my bad. I'd forgotten to update the deployment URL in WP2Static's Settings. The default is.... https://example.com ;-) After adding the correct URL for my Netlify site and redeploying, everything seems to be working as expected. |
@leonstafford
Wp2Static 7.2 release doesn't work on any fresh installation, It's already been verified independently multiple times and reported almost more than year ago. Could you please confirm if wp2static is not abandonware?
Plugin could not be activated because it triggered a fatal error.
The text was updated successfully, but these errors were encountered: