WordPress.org

Ready to get started?Download WordPress

Forums

Advanced AJAX Page Loader
[resolved] Some Minor Bugs (42 posts)

  1. travisavery
    Member
    Posted 2 years ago #

    It's all good, don't stress about it too much. I can respect wanting to sit down and test them all properly. These bugs are cosmetic at best, so I am pretty sure we can either wait, or just get over them. I don't want to eat up too much of your personal time.

  2. Dean Williams
    Member
    Plugin Author

    Posted 2 years ago #

    Travis, I had a brainwave. Try my latest release, I think I cracked the problem :)

    Working in my test cases here ;)

  3. Dean Williams
    Member
    Plugin Author

    Posted 2 years ago #

    Next thing is the HTML special characters, and then I will get onto fixing the # links as reported.

  4. travisavery
    Member
    Posted 2 years ago #

    Once again, you are awesome! Thanks man!

  5. DanStudio
    Member
    Posted 2 years ago #

    Greatest work ever, Dean!

    2.4.7 works fine! Thank you!

  6. leonuts
    Member
    Posted 2 years ago #

    why do i keep having 2.4.7 update in my update panel even though I've updated it?

  7. leonuts
    Member
    Posted 2 years ago #

    Just a suggestion of maybe create a setting page where custom loading gif and element other than 'content' are kept upon updating.

  8. travisavery
    Member
    Posted 2 years ago #

    @Dean Williams Great work (as usual) on the lates update. Works like a charm.

    @leonuts That is a good suggestion, but I would label it as a nice to have. It would make it easier for the average person, however there are several ways to go about changing the loading image right now.

    @Dean I don't know if there is an "official" way to go about doing this, however you may want to add something to the FAQ.

    1. First Option: Replace "loading.gif" in the plugin folder, either by unzipping the plugin or via ftp.
    2. Second Option: In the plugin editor, open the file "advanced-ajax-page-loader.php", find the code shown below.

      Change the number in "new Image(110,64)" to the width and height of your image.

      Then replace "<?php echo get_settings('home');?>/wp-content/plugins/advanced-ajax-page-loader/loading.gif" with the URL of the image you want to use.

      if (document.images){
            AAPLloadingIMG = new Image(110,64);
            AAPLloadingIMG.src = "<?php echo get_settings('home');?>/wp-content/plugins/advanced-ajax-page-loader/loading.gif";
          }
    3. Third Option: Open "ajax-page-loader.js" find and replace the code within the <center> tags whatever you want.
      $('#' + content).html('<center><p>Loading... Please Wait...</p><p><img src="'+AAPLloadingIMG.src+'" border="0" alt="(Loading Animation)" title="Please Wait..." /></p></center>');
  9. travisavery
    Member
    Posted 2 years ago #

    The only reason I recommend the third option at all is because that is how I am doing it. Instead of an image, I am using a div with a background. Then I use CSS to replace the image if the person is on a retina display. If I weren't doing all that I would just replace the image... lol.

  10. DanStudio
    Member
    Posted 2 years ago #

    ok, that's what i've found.

    1. as it said in changelog,

    Anchor links (hash (#) links) are now ignored by the ajax process.

    works just fine for links to the same page, but clicking a link with # for another page does not use ajax. So there probably should be a check whether link follows another page or not.

    2. plugin shows "Error! There seems to be a problem, please click the link again." instead of showing "404" page. Seems quite logical in some way, but on the other hand sometimes we need to use customized 404-page, so... a tiny problem here ;)

  11. Dean Williams
    Member
    Plugin Author

    Posted 2 years ago #

    Hey Dan.

    1. Yes I know it ignores anything with a #, perhaps at some point I will code a way to emulate the anchor method completely so instead of allowing it to "fall back" to the browsers implementation we can process it. This would then fix this issue.

    2. I understand your logic with this one, but because of the way AJAX works, instead of showing 404 pages, you would just show "connection problem" message. AJAX returns a reason and everything for us so we can give detailed information on the error that happened.
    Showing 404 just confuses the situation and makes the user believe a F5 might fix the problem, when in fact they could just click the link again if possible!

  12. DanStudio
    Member
    Posted 2 years ago #

    well, sometimes the link is quite correct, but some content is shown only to registered users, while guests get customized 404.

    but anyway, this sounds like my personal problem and wish, probably i'll get it work some other way.

    thanks for your patience and work.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic