Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • jsventer Friend
    #183360

    We have been waiting for an upgrade to JA_Wall 1.0.5 to achieve compatibility to K2 2.6.2. It looked like 1.0.7 was about to be that release. But after upgrading JA_Wall template and the rest of JA_Wall plugins we lost the website (http://www.thecult.es).

    I’ve seen this error in the logs:

    PHP Fatal error: Call to undefined function jaTpl_getBodyClass() in /var/webs/thecult/templates/ja_wall/index.php on line 104

    I’ve rolled back to 1.0.6 and the web is back in business. I must also point out that the upgrade and rollback process has been a bit tricky, since both of them appeared to last forever.

    I’m a bit worried, since the changelog for 1.0.7 reveals errors with the asides, which has been a major trouble in our site. Also, it’s remarkable the short distance between 1.0.6 and 1.0.7. I think we are now sitting in a non-stable release. Also, the plugins upgrade were ready for 1.0.7. and now we are an step back. I suppose they are backwards compatible.

    Could you provide some advice?

    Regards:

    Javier

    Wall Crasher Developer
    #477447

    Hi jsventer,

    I hope you did not customize heavily on your site.
    As I can see, you have use old index.php file. Please update this one.
    If you have do some heavy customize, just revert back to 1.0.6.
    Or you can try with our new functions:
    – WallHelper::getBodyClass() instead of jaTpl_getBodyClass()
    – WallHelper::isGridView() instead of jaTpl_isGridView()
    – WallHelper::hasAside instead of jaTpl_hasAside
    – WallHelper::hasSidebar() instead of jaTpl_hasSidebar()

    I think you should use our new file and try to clone those modify to new file.

    Regards

    jsventer Friend
    #477558

    Hi Wall Crasher:

    We have no actual customization on the template. The actual modifications are in the layout templates and are related to the sizes of the body and the asides. I think I modified index.php because I found that in this wonderful responsive template, the facebook comment box had a hard coded width. This is the only major change I remember and it’s not such a big change.

    Actually, according to the update documentation, the conflicted files (this is the case of the index.php) are overwritten, so I don’t understand why the system is not modifying the calls to the former jaTPL functions. Are you suggesting I should update the template manually? Maybe using the Joomla extension manager instead of JA_ExtManager?

    Regards:

    Javier

    Wall Crasher Developer
    #477590

    Hi Javier,

    I am sorry for this. We just re-structure coding to make it more clean and easier to maintain.

    Yes, you can just replace those functions in index.php file or just use the new file and copy what you have modified to the new index.php.

    You can also revert back to 1.0.6 if you want.

    Please pm ftp/admin information if you have problem, I will help you.

    Regards

    jsventer Friend
    #481221

    Hi Wall Crasher:

    I’ve finally decided to do the upgrade because there was a lot of things that weren’t working as expected and some of the things appeared to be crrected in the changelogs. I’m not exactly happy about the final result because I’ve lost the dynamic arrangement of the articles in the wall. I might close this topic but I want to share some things with you. Maybe you could take them into account for a future release:

    The Extension manager didn’t work as expected. It hadn’t work as expected for quite a while. The documentation said the conflicted files are overwritten and this is not true. It hasn’t been true for a couple of upgrades. My conflicting files didn’t look not even like the 1.06 release. Once launched the upgrade to 1.07 they remained unchanged.

    The files that the system detected as conflicted because of my modifications had no actual modification. Two additional empty lines at the end in one case. I hadn’t touched the files, not even for reading the contents. I think that there might be a mismatch between the release repository and my actual installation. I don’t know if someone else has show up with this.

    After doing the upgrade I had to modify the file template_tools.php which, once again, has misspelled the names of the aside modules (aside-1 instead of aside).

    Regards:

    Javier

    jsventer Friend
    #481231

    Another one from today revision around the upgrade process.

    I’ve found these entries at the site error log

    File does not exist: /var/webs/thecult/templates/ja_wall/js/jquery.jbk.js, referer: http://www.thecult.es/opinion/el-necronomicon-y-las-spanish-logomaquias.html
    87.223.151.195 – – [27/Jan/2013:04:48:11 +0000] “GET /templates/ja_wall/js/jquery.jbk.js HTTP/1.1” 404 312 “http://www.thecult.es/opinion/el-necronomicon-y-las-spanish-logomaquias.html” “Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17 AlexaToolbar/alxg-3.1”
    File does not exist: /var/webs/thecult/templates/ja_wall/js/jquery.noconflict.js, referer: http://www.thecult.es/opinion/el-necronomicon-y-las-spanish-logomaquias.html
    87.223.151.195 – – [27/Jan/2013:04:48:11 +0000] “GET /templates/ja_wall/js/jquery.noconflict.js HTTP/1.1″ 404 319 “http://www.thecult.es/opinion/el-necronomicon-y-las-spanish-logomaquias.html” “Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17 AlexaToolbar/alxg-3.1”

    These are remains of an incomplete or unfinished update process. I think I will need some help to arrange this.

    Regards

    Javier

    Wall Crasher Developer
    #481250

    Hi Javier,

    If you have not modified much on your site, you can try to use Extension Manager (Joomla) and reinstall ‘ja_wall’ template package and ‘japager’ system plugin.

    Also please pm your site information so that I can help you.

    Regards

    jsventer Friend
    #481423

    Hi Wall Crasher:

    As I told you there is no significant modification in my site. At least not the one that might be producing the effects I was describing. Actually, I’ve cornered my modifications to two files: css/layout-hd.css and css/layout-wide-extra.css.

    The rest of the modifications were “imagined” by Ja_ExtensionManager. I’ve reviewed all the updates of my site and I’ve discovered that there was several files that had not been updated for a while, not just in this releas. Not only index.php, wall.js script.js and my actually modified css files. Also after doing the upgrade with the JA Extension Manager, iscroll.js was different from the actual iscroll.js from the 1.07 distribution. I don’t know the reason for the differences. From the initial setup I have been using JA Extension Manager, so the reason must be that.

    So, since I have no special modification, I reinstalled from Joomla Extension Manager, and now I have my site properly updated. Still I had to correct the template_tools.php file as I told you in my previous post, because the aside modules don’t show with the original definition in the file. It’s curious, because it was the first error I found in the initial installation with 1.04 and it had been corrected.

    I’ll close this topic. I might have some other questions about lazyload, social feed and images in K2 (see JAECPLGSOCIALFEED-50). But upgrading is no longer a problem… for me.

    Regards:

    Javier

    Wall Crasher Developer
    #481429

    Hi Javier,

    I am glad that your problem has been solved.
    About other questions, can you give me the thread link?
    I just checked, JAECPLGSOCIALFEED-50 has been resolved.

    Regards

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

This topic contains 9 replies, has 2 voices, and was last updated by  Wall Crasher 11 years, 10 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum