I am getting Fatal error: Call to undefined function new_smarty() in /************/amember/admin/index.php on line 23 I figure I have to upgrade the version, however, to find out which version I have I have read I have to go to the admin panel to check and as you can see I cannot do this. Anyone any ideas how I can find out which version the script is. Is it normal for the software to crash/lock/insert whatever term used here, a day after the free upgrades run out. Any help appreciated, I will try to stuggle on with it until the cavalry arrives.
This problem is not related with free upgrades or anything in aMember itself. Please contact your webhosting and ask them if they have any automatic processes that seek for eval(gzinflate(...)) strings in PHP code. If they have any, please ask, no - do not ask, REQUIRE them to disable this at least for files named "rconfig.inc.php". They may think it is some kind of code inserted by hackers, but it is legitimate part of aMember code. So if they just remove code that their system do not like, without even noticing the customer, it is completely unacceptable. Ask them also to immediately restore your file amember/rconfig.inc.php from backup in the original form, as it was before their changes.
I got this error when I tried to upgrade 3.1.2 to 3.1.4: Fatal error: Call to undefined function: new_smarty() in ****/public_html/amember/admin/upgrade_db.php on line 20 Is this related to what you wrote in the previous reply?
I got the same error migrating a working 3.1.2 to 3.1.4. I've confirmed the files were uploaded in binary. In fact, I've tried now multiple times. Ticket opened.
I've been seeing this on quite a few upgrades- i also have a ticket in. Hope it gets solved soon! Was told to run: /amember/admin/upgrade_db.php However this also gives an error: Fatal error: Call to undefined function new_smarty() David
Looks like they fixed it. "I just have reupload rconfig.inc.php." Suppose you can get this out of the full version of 3.1.4 David
After being taunted by tech support (Anton), I saw this message. Apparently the rconfig.inc.php that was included in the 'upgrade kit' was not the right version. To solve the problem, I downloaded the full version and extracted rconfig.inc.php and moved that into the upgrade kit. The upgrade then took about 2 minutes and worked flawlessly. I hope they are able to make this switch before others have to endure the hand-banging... Thanks for pointing this out and saving me the time!
I couldn't afford the waiting time for support to give an answer. I downloaded the new version and reinstalled.