studiomeyerio

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [StudioMeyer Transparency Toolkit for the EU AI Act] Mark all existing articles as AI
    Plugin Author studiomeyerio

    (@studiomeyerio)

    2 weeks, 3 days ago

    Hi fraprodk,

    You’re right, in 1.0.0 there is no bulk option, only the per item toggle in the
    editor. Going through a whole archive one post at a time is exactly the thing
    nobody should have to do, so I built it. It is out now as 1.1.0.

    There are two ways.

    On the Posts, Pages and Products lists there are two new entries in the Bulk
    actions dropdown, “Mark as AI-assisted” and “Remove AI label”. Tick the items you
    want and apply. Those lists also get a small “AI” column so you can see at a
    glance what is already marked.

    For a whole archive there is a new page under Transparency Toolkit called Bulk
    labeling. You pick the content types, choose between published items only or
    everything except trash, tick the confirmation and run it. One run changes at
    most 200 items. If content is left over the page says so and keeps your settings
    selected, so you just run it again. The same page removes the label again, so the
    labeling is reversible. Trashed content is never touched.

    One thing worth knowing: removing the label also clears the optional detail text
    on those items, and that text does not come back if you mark them again.

    Thanks for asking, this went straight into the release.

    Forum: Plugins
    In reply to: [AI-Ready WP] Notice error in debug-mode when running AI-Ready WP
    Plugin Author studiomeyerio

    (@studiomeyerio)

    3 months, 1 week ago

    Hi Ruben,

    Thanks for the report, you were right. Fixed.

    Version 4.1.1 is on the way to WordPress.org and should show up as a plugin update within the next few hours.

    While I was looking at it I noticed that WordPress 6.9 actually enforces three things on the Abilities API, not just the hook. Documenting them here in case other plugin authors run into the same wall:

    1. Hook: add_action( 'wp_abilities_api_init', ... ) instead of init. That was the notice you saw.
    2. Required category property: without it the ability is registered but then immediately dropped with a “The ability properties must contain a category string” notice. AI-Ready WP now registers its own category airewp on wp_abilities_api_categories_init and all four abilities reference it, which also groups them cleanly in the MCP Adapter and admin views.
    3. Property rename: 'callback' is now 'execute_callback' in 6.9. The old key triggers the same class of notice.

    Smoke tested against WordPress 6.9.4. All four airewp/* abilities (get-business-info, get-readiness, search-content, plus the optional get-services) are sitting in wp_get_abilities() and debug.log stays clean.

    The Pro variant had the exact same bug across the four WebMCP tools (submit-lead, book-appointment, search-products, get-analytics-summary), 1.2.1 ships the same fix.

    If you spot anything else, let me know in the forum or via issue. You helped make the plugin properly 6.9 ready.

    Cheers Matthias / StudioMeyer

Viewing 2 replies - 1 through 2 (of 2 total)