News Show Pro GK5 after update problem 1064

GK User
Fri May 29, 2015 8:21 pm
I have updated the module News Show Pro GK5, in position header_left and my site is not working, giving error 1064.
I have the above module in two sites and both, after update, have the same problem.
I disable it in one and the site is working but I need to enable it. So, definitely is the above module problem.
Url: http://www.lexconscientia.sg
In the other site, http://www.lexconscientia.co.uk, (it is not online), I created a Custom HTML module in the same position to keep it working and work on it to finish it.
Why updating a module used in this template is causing such a problem? It doesn't make sense.
I think that Gavick has to take care and fix the bugs before launching module updates for its templates compatible with the relative Joomla version.
Any help please?
User avatar
Senior Boarder

GK User
Sun May 31, 2015 9:23 am
Please follow this path:

0) Install new current version of NSP GK5 (re-install)
1) Open module in edit mode
2) Click Refresh button in your browser
3) Change data source to another from list
4) Change order of showing items
5) Save changes - check on front page
6) If okey, change data source back to option which you have at the beginning
User avatar
Moderator

GK User
Sun May 31, 2015 1:03 pm
Thank you for your kind reply.
A collaborator has fixed the problem before your answered, I don't know yet how he done it. I will keep in mind your solution for any future problem.
I would like add that no other update of module needs such a procedure. I think you have to publish some instructions for the modules they need a special procedure like this. It is awful somebody suddenly see his site not working because of a normal module update, trying then to find solutions.
I am getting the opportunity to ask a question about this module. Is it any way to use external links than using aricles, keeping the display as it looks now (not important if date not be shown, although I would like keeping it)?
Thanks!
User avatar
Senior Boarder

GK User
Mon Jun 01, 2015 6:00 pm
Actually this error shouldn't show never again. It is hard to admit but it was a developer mistake and before he could fix it out, some people already downloaded the "buggy" version. Particularly it is also browser cache issue - sometimes clearing just the cache helps and solves all the issues.
User avatar
Moderator


cron