10 thoughts on “More…”

  1. Just tested your Plugin and it’s really awesome! Thank you for your effort and time in developing this plugin. As I’m a developer I would like to give some opinion. I think if you can Improve some issue and can add some few more options will boost up this plugin. I believe it’ll spread widely.

    As a developer it’s ok, But from an owner’s perspective they want to earn from their site. So you can improve Adsense issue. In your documentation about Adsense can give a solution for a small site but for large and more content full site (like news, blog, comparing site) will not be able to use because it’ll decrease their advertising revenue (E.g. Adsense auto ad). Also it is not always possible to keep ad code outside the swapped elements.

    Another issue is, some webpages do not really need Ajaxify because the development structure of these pages may crash due to its use. So should give an option to keep a single or multiple pages can exclude from Ajaxify.

    Language translation, now a days it is also an important part of web development. Most websites are multi language supported. (Say, I’ve website example(.)com and it’s language are English if I navigate to example(.)com/fr it’ll be French. But it’s not happening.

    You should also include some example code snippet in your documentation.

    So far I have mentioned these issues and I will check further to see if any suggestions can be given. Thank you.

    1. Hi Hasnat!

      Thanks for the awesome feedback – much appreciated!
      It’ll take me a while to process all that 🙂

      Will translate the points you made into some GitHub issues, in order not to lose them in the course of further comments from users.

      Talking about GitHub issues – if you like, maybe you can have a look at these (I’m busy with them at the moment):

      Plain vanilla triggering of custom events

      and

      Appropriate handling of DOMContentLoaded

      (Just wanted to give you a quick reaction…)

      Thanks a bunch!

      Regards, Arvind

      1. Thank you so much for your attention and very quick response. First of all I am trying to find a suitable way to display ads. I will definitely let you know if I can find a suitable way.

        1. I’m the one to say “thanks”!

          Interesting, that you think the Adsense issue is the most impending (strategically).

  2. Hi there, I’m struggling to get this working. It saves the data without reloading the page, but the form gets deleted. This error is produced in the console, any ideas?:

    Uncaught ReferenceError: AOS is not defined
    at :2:3
    at _apptxt (ajaxify.min.js:1)
    at _addtxt (ajaxify.min.js:1)
    at _onetxt (ajaxify.min.js:1)
    at classScripts.a (ajaxify.min.js:1)

    1. Hi Gabriel,

      Did you get it going in the meantime?
      Your console error was a bit long, I have truncated it.

      Do you have a link to your site?

      Regards,
      Arvind

  3. Hi Arvind,

    tested new prefetch features a bit. Filters are working great, but I noticed one flaw for prefetch hover option itself. After some code digging and options changing I realized that prefetch doesn’t work for new links loaded inside content div(s), like hoverIntent detection is not attached to them. In my case there are #dynNav, #dynData and #dynFoot dynamic containers (dynamic navigation is for “active” classes to highlight current page link and eventually to load new links while switching to admin section). So after first navigation link inside #dynNav gets clicked that container is populated with new (sometimes same) links and there is no hover reaction anymore.

    Tested it on 4nf.org also, navigation bar is static and links inside are prefetching always, but those inside dynamically loaded pages are not reacting.

    Best regards,
    Edin

  4. Hi,
    You’re plugin is really good, thanks!
    The only problem I’m having is using it with Typekit. The way Typekit works is that you put an embed script into the , this is run and it attaches a link to your font. My problem is that when a new page is requested with Ajaxify the link to the font disappears from the head and I end up with the fallback font. I can’t figure out why this is happening. I’ve tried putting Typekit in inline skip but it seems like since the generated link to the font is missing from the incoming page it’s being removed from the current page. Do you have any idea how to fix this?

    1. Hi Andrew,

      thanks for your interest in the plugin!
      I don’t have a clue unfortunately, because I’m not acquainted with Typekit…

      Cheers!

    2. Hey Andrew,

      I’m having exactly the same problem, did you ever manage to find a fix for this?

      Thanks,

      Matt

Leave a Reply to Gabriel Thornton Cancel reply

Your email address will not be published. Required fields are marked *