AbanteCart Community

Shopping Cart Operations => Support => General Support => Topic started by: scorpion on July 22, 2013, 01:57:01 AM

Title: Can't access Content Page In Admin Since Update from 1.1.5. to 1.1.6.
Post by: scorpion on July 22, 2013, 01:57:01 AM: Hi I recently upgraded to the latest version of AbanteCart Cart and cannot access the content menu in the admin. It says there has been an error processing this request. In the error log this is what I find
Grid column model contains reserved column name ("parent"). in /home/scorpion/public_html/admin/controller/common/listing_grid.php on line 101
Thanks andrew
Title: Can't access Content Page In Admin Since Update from 1.1.5. to 1.1.6.
Post by: lloydcodrington on July 22, 2013, 05:12:10 AM: After completing the update the first time I went to use the Content feature in the admin panel I get the following error message:

There has been an error processing your request
Please check error log for more info. You can check error log in the control panel if it is functional. Otherwise, refer to error log located in your web server
Go to main page

The log has the following line:
2013-07-22 8:15:57 - load error: AbanteCart core v.1.1.6 Error: Could not create grid. Grid column model contains reserved column name ("parent"). in /home/surestri/public_html/store/admin/controller/common/listing_grid.php on line 101

Please can you assist?

Regards,
Lloyd Codrington
Title: Re: Can't access Content Page In Admin Since Update from 1.1.5. to 1.1.6.
Post by: abolabo on July 22, 2013, 08:15:40 AM: can you say is your file
public_html/admin/controller/pages/design/content.php is the same as https://github.com/abantecart/abantecart-src/blob/master/public_html/admin/controller/pages/design/content.php ?
Title: Re: Can't access Content Page In Admin Since Update from 1.1.5. to 1.1.6.
Post by: scorpion on July 22, 2013, 05:53:50 PM: Hi The file must be different. I copied the content.php file from your repository and replaced my content.php file and I can now successfully open the content page. Thanks for the solution Andrew