Steven Ayers

Thank you for sharing that. Closing this ticket.

-Steven

@tapulator,

I saw your reply last night right before we took off. I’m glad you figured out what the issue was. Could you possibly post that Apache config example here same problem can benefit from your solution?

If you need anything else, please let me know.

-Steven

@tapulator,

Thanks for using Fix Alt Text. I remember this issue from a while back (didn’t realize it was 3 years ago!).

We never received confirmation about whether our solution actually fixed that person’s issue or not so we just closed the ticket.

Id be happy to troubleshoot this issue again. I will need to replicate it on my end and go from there. Please provide the following details:

• WordPress Version
• PHP Version
• Nginx, Apache, Or other web server (and version)?
• Who are you using for hosting? (Make sure we are compatible)
• Are other cron jobs running? Install Cron Control to see if all your wp cron jobs are stacking up and past due.

Thank you.

-Steven

@farisdevomer,

Thank you for the kind words and for using the plugin. It is users like yourself that are helping improve this plugin by reporting issues when you discover them. We greatly appreciate that.

-Steven

@benlk,

I am writing to a text file with a list of post IDs that need to be scanned (queue). Storing these IDs in a transient (the database) is not feasible due to the queue rapidly changing as the scan progresses (removal of scanned IDs). I started down that path originally and then get into batching and inevitably migrated to using a text file.

Rapidly modifying a text file is not a heavy task. The CPU load is a problem for large databases. This was designed to accomodate 100K+ posts across a 5+ site multisite setup.

FYI: Any changes I make to the scanning process will also affect another plugin called WhereUsed.

-Steven

• This reply was modified 9 months ago by Steven Ayers.

@farisdevomer,

I apologize, as I never saw the email notification about this support request. Thank you for using FixAltText by the way. If it is still relevant, here is my response:

It is odd that the user is experiencing a session expired error. This error means that it failed the nonce check for doing an inline edit. Here’s the scenarios where this would fail:

• (not likely) – Browser has cached the Fix Alt Text admin page, thus an old nonce is in the HTML of the page. I don’t think this is the case as the browser should not be caching the admin pages.
• (not likely) -The Fix Alt Text admin page has been open for a while (more than 12 hrs) and the once has expired, so when the nonce in the HTML is used to perform an AJAX request the nonce is invalid. I don’t think this is the case as you said you have the user logout and log back in and still was having the issue.
• (not likely) – You are performing an AJAX request from a page that shouldn’t be. This is what an attacker would do…so this is not in the scope of this scenario.
• (Maybe) – I’ll have to look and see if I am doing some AJAX requests on the main menu items (not sure if I am or not on this plugin). This could be interfering with the nonce validation.
• (Possible) – The only other thing I can think of is some sort of odd page caching or object caching on the server. Have you tried clearing your website cache? If this fixes it, then you need to exclude the /wp-admin/* from being cached by your caching plugin or hosting.
• (Likely) – It sounds like other users could inline edit successfully, correct? If so, then the issue is either specifically related to that user (doubtful), or something the user is doing is exposing the issue in the system (likely).

Replicating the issue on my end:

Just for clarity, can you provide me the relative link where the problem occurs? The link should start with /wp-admin/… I don’t need the full URL just this portion of it. I want to attempt to replicate the issue on my end. Maybe also provide some step-by-step instructions on what actions you are taking to get to the page to replicate the issue. I know where the issue occurs but the steps in how you get there may provide a clue as to what is causing the issue.

-Steven

@websitesbuiltforyou,

Also, this bug affected another plugin called WhereUsed. The fix will be released in version 1.5.0 of WhereUsed. Unfortunately, it will take a little longer for that release as it is a big release.

-Steven

@websitesbuiltforyou,

Thank you for the kind words. Also, we really appreciate that you reported a bug to us and provided the solution!

-Steven