slapbox

To clarify the question, specifically how would we get v1.3 to come above those? I’ve experimented with the code like from the API docs that looks like:

download_monitor()->service('version_repository')->persist($dummy_entry);
download_monitor()->service('transient_manager')->clear_versions_transient($dummy_id);

But the end resulting list in the UI looks like:

– 1.2
– 1.1
– 1.3
– 1.0

The newly added item always seems to come second to last, even if the created date and version is larger, and I see persist takes no arguments, so is there some special logic for ordering I’m overlooking?

I’d be very grateful for a pointer here!

Thank you again!

Thanks for the reply @beatrice12!

In the meantime, could you give any hint about how to add a new version to the list of files for a given download item?

For example, if the download current has listed versions like

– 1.2
– 1.1
– 1.0

How could we insert a version 1.3 above those?

Actually I think we were probably wrong… looks like we had Yoast a couple versions behind and it seems to work after updating.

@maybellyne thanks for your reply.

I think there’s more here than just the broken card previews. Card previews seem to be broken for every site I try; but those sites will still render if we post them to Twitter (eg nytimes.com links like https://www.nytimes.com/2022/07/28/us/politics/manchin-schumer-climate-tax-deal.html)

But our site that uses Yoast neither renders in the validator NOR on Twitter.com.

Additionally could you comment on whether this change might be required in Yoast? It’s mentioned in the thread you linked as a solution and several people have said it fixed their issues: https://support.google.com/blogger/thread/170510968?hl=en#

I do strongly believe that Yoast needs to address this on their end, based on my reading.

Hey @wfphil, thanks for your reply!

Unfortunately I’m not seeing that option. Can you possibly provide a screenshot of what we should see? I even searched the page’s source code for “Start new” and “New scan,” but those phrases don’t appear. I’m looking under the “Scan” tab. I know long ago that the option to start a manual scan was clear enough, but it truly does seem to be missing for us.

Actually, it just seems like the inactive logout is failing more and more frequently now. Currently entering hour 3 of the 15 minute auto-logout period.

Hey @mbootsman thanks for your reply!

Maybe this is a non-issue. I had sworn I was seeing the ahab.js file in the frontend output for non-logged in visitors, but I’m not able to reproduce that right now unless I forgot to clear some cache. If I do recreate the issue I’ll update here.

Thanks again for your reply, and thanks for the great plugin!

Generate password is also broken here

I’m not an expert in WordPress, but actually I think this is because the plugin makes a weird choice, I guess, and the individual feature requests are of type ‘Page’?

According to Debug This there’s no taxonomy defined for the pages, despite the fact the plugin adds a custom post type.

Unfortunately even if we apply to all of the post type, archives, and check “Auto-select new children of selected items” – the outcome is the same.

Any advice?

Looks like I needed to use the “Extend this user to” feature. It’s a bit confusing, but it all seems to work. Thanks for sharing your great work!

Ran into the bug again. Trying your advice now and will report back if it persists.

Thanks for your reply @wfadam! This is the first time I’ve noticed it happen, though I can’t say for sure this is the only time it’s happened. Alerts seem to be working fine otherwise. If I see this issue again I’ll try your suggestion and update you here.

• This reply was modified 4 years, 1 month ago by slapbox.

@wfdave we launched a new version of our site with a lot of changes, but the issue persists. An otherwise great plugin, but I’d love to get this working!

Thanks for the quick reply @waseem_senjer.

I noticed today there’s also a JS file that seems the same way. The only contents are:

/*!/wp-content/plugins/controlled-admin-access/public/js/controlled-admin-access-public.js*/(function($){'use strict'})(jQuery)

Thanks again for your awesome work!

@mguenter, looks great! Thanks so much!