Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • dodoni Friend
    #125597

    hello.
    after move of the website to a new server with php5 (instead of php4 used before) everything works fine except the headline refresh. It is stuck only in the first article out of 10 that there are declaired for headlines.

    Edit: the issue happens in IE7.

    I use JA News 1.1.1 and joomla 1.0.12

    I tried to upgrade or downgrade to other versions of ja-news, with no result.
    I googled it, i searched the forum here a lot, bout couldnt come to any result.

    Please provide some help. Headlines are one of the most improtant things in my frontpage.

    Thanks in advance for any help.

    dodoni Friend
    #238816

    Please give some help.

    I ve read all of the threads in teline, i saw others having a similar issue but no solution for me yet.

    bigrk Friend
    #238818

    There are issues with Joomla and PHP5. This would be a Joomla issue and you would need to search their forums or you can wait and upgrade to the newest version of the Teline template for Joomla 1.5 Stable when it is released. The problem with any of the JA News modules that you would be trying to use is that they are at best 6 months old. You could also contact your hosting company and see if you can go back to PHP4 which is what I would recommend..

    dodoni Friend
    #238831

    this is really bad news, cause i cannot go back to php5.
    Also, i m not planning to upgrade to joomla 1.5 because of the many components and modules i have installed and it seems that they probably wont work with 1.5

    Thank you for your answer.

    PS. By googling the error that IE gives, i found out that in other projects, the problem was solved by altering something that had to do with encoding. For example, the exact same error as mine was solved by someone with changing utf-8 to UTF-8 which is the way IE understands it.

    I mention the above in case someone has an idea on how to solve this.

    dodoni Friend
    #239007

    in case it helps someone,
    the problem was actually an encoding issue.
    My site is in utf and the server was in iso-8859-1.
    By changing the server charset to “none” the problem solved.

    bigrk Friend
    #239018

    <em>@dodoni 40263 wrote:</em><blockquote>in case it helps someone,
    the problem was actually an encoding issue.
    My site is in utf and the server was in iso-8859-1.
    By changing the server charset to “none” the problem solved.</blockquote>

    This is good to know. Thanks for the update dodoni! 🙂

    mj1256 Friend
    #239093

    maybe not a long term solution but you are correct that there may be a conflict, but changing to none may not be the answer,

    Character set encoding is one of the technical “under the hood” website items that is difficult to understand and needed as you must define a character set. for the browsers to render your website correctly.

    ascii has be superceeded bu UTF-8
    all browsers are designed to recognize UTF-8 and iso-8859-1

    The standard right now is for UTF-8 encoding, if you are using cpanel and go to edit any file (through cpanel) it will give you an option to change to UTF-8 and this will automatically set your ISO to the proper one and will remove the conflict.

    I suspect the problem was that you were using plain UTF and just needed to change it to UTF-8

    I hope this helps 🙂

    dodoni Friend
    #239108

    mj1256,
    my whole website (files, db, everything) was 100% UTF-8. The site was running like that and absolutely correctly in the previous server. After moving it to a new server, started the conflict.
    I search a lot about the issue (although i m not familiar with this kind of issues).
    Many threads in google, lead me to this action i did.
    Also, it happens that i own these 2 servers, so i tried to compare them, in every single option and that was the only difference i could found. And that did solve the problem.
    But i can undestand what you mean when you say that there may be better options.

    mj1256 Friend
    #239158

    yeah, you still need it on for browser compatibiltiy, it looks like to old server was set up correctly and the new one wasn’t. Turning it off and setting it to none, may on the surface seem like a solution, but as I said, it is not. browsers look for that character encoding to know how to render your site.

    there are many posts here about how scripts and code stop working on their sites because a & is converted to &, this is do to this character encoding issue and is solved with the correct settings.

    I adminisister my own server and websites, i have everything set to utf-8 and I have none of these issues anymore

    as you said, your old server was set to utf-8 and all was well

    well…i was just trying to help…good luck 🙂

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

This topic contains 9 replies, has 3 voices, and was last updated by  mj1256 16 years, 9 months ago.

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