Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor lmrhody

    (@lmrhody)

    Hi Jim,
    We have not heard of Google alerts necessarily taking a longer time to load. One possible way to see what is causing the delay is to set up a log file. The instructions on how to do that can be found here: https://github.com/PressForward/pressforward/wiki/Debug.

    Good luck, and keep us posted!

    Hi Jim,

    Also, the most common source of delays on the All Content page is large images included in the RSS feeds you’ve subscribed to. We’re working on a method to avoid pre-loading them, but it isn’t in place yet.

    Do you think that is something that you’re encountering on your feeds?

    -Aram

    Thread Starter doctorproctor

    (@doctorproctor)

    Thanks, both! Yes, could well be that our GoogleAlerts are queuing up image files. We’ll also move forward in setting up a log file to get further info. (Quick note: your link specifies wp-includes/uploads when it should, I believe, say wp-content/uploads.)

    Regards,

    Jim P.

    Thread Starter doctorproctor

    (@doctorproctor)

    Quick note: no entries in log after running PF > All Content; tried a few times. Permissions set at 664. Will update to latest PF soon and see if that changes things at all.

    Thread Starter doctorproctor

    (@doctorproctor)

    Note, with update I’m now seeing (string ID changes with each load)

    string(151) "PF screen trace: ID: pressforward_page_pf-options; action: ; base: pressforward_page_pf-options; parent_base: ; parent_file: ; post_type: ; taxonomy: ;"

    at top of each PF page. Also curious as to difference btw log file (which still is not being written to) and debug log accessed via PF > View Log, which I can access.

    Jim P.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘delay in loading content’ is closed to new replies.