Home » Topics » Priority Support » Widget Factory fatal error

Widget Factory fatal error

ACF Widgets Support Priority Support Widget Factory fatal error

This topic contains 12 replies, has 2 voices, and was last updated by  Abi Cushman 3 years, 8 months ago.

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #2543

    Abi Cushman
    Participant

    Hi Daron,

    I’m getting a fatal error when I try to activate the plugin. (I have Version 1.4). Here is the full text of the error:

    Fatal error: Access level to ACFW_Widget_Factory::__construct() must be public (as in class WP_Widget_Factory) in /Users/Abi/Sites/whs biz/wordpress/wp-content/plugins/acf-widgets/includes/ACFW_Widget_Factory.php on line 46

    Any insight into this?

    Thanks!
    Abi

    #2549

    Daron Spence
    Keymaster

    Hi, that error was fixed in 1.5 which should be available as an update in your dashboard. If you’re not sewing it, you may need to click the “check now” button to clear the transients cache.

    #2550

    Abi Cushman
    Participant

    Hi Daron,

    I cleared the cache in the database, but it’s still not seeing an update available. I also checked on another site that I used it on to see if it was showing an update to 1.5 there, and it wasn’t.

    Any advice?

    Thanks!
    Abi

    #2551

    Daron Spence
    Keymaster

    You can download the latest version from your purchase history here on the site. Make sure the license key is present on both of your sites.

    #2554

    Abi Cushman
    Participant

    Thank you, Daron. That worked.

    #2555

    Daron Spence
    Keymaster

    Did you have to download it or was it a license issue?

    #2556

    Abi Cushman
    Participant

    Well for this new install, I had to just download the new version b/c I got the error when I tried to activate the plugin. (So I wasn’t able to put in the license key into the settings.)

    But I checked on the other site, and the license is in there, but it says “License Key: site_inactive” for some reason. (And the submit button is to Deactivate License.) The plugin is working though, so I’m not sure what the deal is there. Should I click to deactivate it and then put the license key in again?

    #2557

    Daron Spence
    Keymaster

    Yeah you can deactivate it and reactivate. You can also deactivate sites from here as well, I just don’t advertise the feature.

    #2558

    Abi Cushman
    Participant

    Oh yes, I see now that the live site URL wasn’t in the list of Site URLs, only my local version was. I added the live site, and that solved the problem.

    Thanks so much for your help!
    Abi

    #2559

    Daron Spence
    Keymaster

    One final question! Did you do a database migration from your live site to the dev site? I can work on adding a buffer to double check the URL even after it’s added but I’m trying to reproduce it first 🙂

    #2560

    Abi Cushman
    Participant

    Actually, I’m looking at the list of urls again, and I see what happened now. When it was on the server before it was live, we were using an IP address to populate and test the site before pointing the domain over. So it was activated for the IP address, and not the actual url. So I probably should have deactivated and reactivated the license once the site went live. I’ll do this in the future.

    So I don’t know if this is possible, but perhaps there could be some sort of alert on the plugin telling people to reactivate the license if they change the WordPress Address (URL) in the settings.

    #2561

    Daron Spence
    Keymaster

    That’s what I was thinking. Maybe a one time admin notice and then persist that notice to any ACFW admin pages. I’ll look into it when I get some more free time!

    Thanks again for supporting the plugin and be sure to let me know if you find any more bugs/errors. 🙂

    #2562

    Abi Cushman
    Participant

    Thanks, Daron, for your excellent plugin and support!

Viewing 13 posts - 1 through 13 (of 13 total)

The topic ‘Widget Factory fatal error’ is closed to new replies.