[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fNduVPMqaAQK_ajeTDJanhO02GVGgPDL6y6E2P3THQZg":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":35,"analysis":127,"fingerprints":234},"acf-flexible-content-layout-thumbnail","ACF Flexible Content Layout Thumbnail","1.0.0","webcentar","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebcentar\u002F","\u003Cp>Extend Advanced Custom Fields PRO – add thumbnail layout to flexible content\u003C\u002Fp>\n","Extend Advanced Custom Fields PRO - add thumbnail layout to flexible content",10,1501,0,"2018-07-11T18:06:00.000Z","4.9.29","4.8","",[19,20,21,22,23],"acf","advanced-custom-fields","field","fields","flexible","http:\u002F\u002Fwww.webcentar.net\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-flexible-content-layout-thumbnail.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,84,"2026-04-05T10:29:06.957Z",[36,57,76,91,106],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":33,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":54,"download_link":55,"security_score":56,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"acf-hide-layout","ACF Hide Layout","1.2.1","Bleech","https:\u002F\u002Fprofiles.wordpress.org\u002Fbleechberlin\u002F","\u003Cp>Sometimes you may need to hide\u002Fremove a flexible content layout from showing on the frontend of the website, but you would still like to keep it in the backend in case you need to re-enable that layout again in the future.\u003C\u002Fp>\n\u003Cp>Of course you can always just remove the layout, but if it’s a complex group of fields with a lot of data, re-creating it later would be a pain. And here the \u003Cstrong>ACF Hide Layout\u003C\u002Fstrong> plugin comes into play. It adds a small button with an “eye” icon to easily disable\u002Fenable flexible layout content without removing it.\u003C\u002Fp>\n\u003Cp>See more info on the \u003Ca href=\"https:\u002F\u002Fflyntwp.com\u002Facf-hide-layout\u002F\" rel=\"nofollow ugc\">plugin website\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002F\" rel=\"ugc\">WordPress\u003C\u002Fa> >= 4.7\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.advancedcustomfields.com\u002Fpro\u002F\" rel=\"nofollow ugc\">Advanced Custom Fields Pro\u003C\u002Fa> >= 5.7\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>The source code can be found on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fflyntwp\u002Facf-hide-layout\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Made by people who brought to you \u003Ca href=\"https:\u002F\u002Fflyntwp.com\u002F?utm_source=WordPress%20Plugin%20Directory&utm_medium=Link&utm_campaign=ACF%20Hide%20Layout%20Plugin\" rel=\"nofollow ugc\">Flynt – The Component Based WordPress Starter Theme\u003C\u002Fa>\u003C\u002Fp>\n","Easily hide the layout of the flexible content on the frontend but still keep it in the backend.",2000,15049,5,"2024-07-19T12:39:00.000Z","6.6.5","4.7","5.6",[19,20,52,53],"flexible-content","hide-layout","https:\u002F\u002Fflyntwp.com\u002Facf-hide-layout\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-hide-layout.1.2.1.zip",92,{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":67,"num_ratings":31,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":17,"download_link":75,"security_score":67,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"flexible-layout-preview-image-for-acf","Flexible Layout Preview Image for ACF","1.4.2","Galaxy Weblinks","https:\u002F\u002Fprofiles.wordpress.org\u002Fgalaxyweblinks\u002F","\u003Cp>\u003Cstrong>Flexible Layout Preview Image for ACF\u003C\u002Fstrong> is a WordPress plugin that enhances the admin experience by adding custom images to the previews of flexible layouts created using Advanced Custom Fields (ACF). This visual aid helps administrators quickly identify and manage various layout blocks within ACF flexible content fields.\u003C\u002Fp>\n\u003Cp>Here’s a link to the documentation for the plugin. This will help you learn more about its features and how to use it.\u003Cbr \u002F>\n\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwp-plugins.galaxyweblinks.com\u002Fwp-plugins\u002Fflexible-layout-preview-image-for-acf\u002F\" rel=\"nofollow ugc\">Documentation\u003C\u002Fa>\u003C\u002Fstrong>\u003Cbr \u002F>\nFor any feedback or queries regarding this plugin, please contact our \u003Ca href=\"https:\u002F\u002Fwp-plugins.galaxyweblinks.com\u002Fcontact\u002F\" rel=\"nofollow ugc\">Support team\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Adds preview images for ACF flexible content layouts in the WordPress admin.\u003C\u002Fli>\n\u003Cli>Automatically detects and applies images stored in your theme directory.\u003C\u002Fli>\n\u003Cli>Allows developers to customize image paths via filters.\u003C\u002Fli>\n\u003Cli>Works seamlessly with the ACF plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How It Works\u003C\u002Fh3>\n\u003Cp>Place your custom preview images in your theme directory at \u003Ccode>\u002Flib\u002Fadmin\u002Fimages\u002Fflexible-layout-preview-image-for-acf\u002F\u003C\u002Fcode> with filenames matching the ACF layout names (e.g., \u003Ccode>layout-name.jpg\u003C\u002Fcode>). The plugin will automatically display these images in the ACF layout preview popups.\u003C\u002Fp>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cp>The following filters are available for customization:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>flexible_layout_preview-image_for_acf_images_path\u003C\u002Fcode>\u003C\u002Fstrong>: Customize the path to load images from.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ccode>flexible_layout_preview-image_for_acf_images\u003C\u002Fcode>\u003C\u002Fstrong>: Modify the array of layout keys and image URLs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later. See the \u003Ca href=\"https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\" rel=\"nofollow ugc\">LICENSE\u003C\u002Fa> file for more details.\u003C\u002Fp>\n","Adds flexible layout preview images for Advanced Custom Fields (ACF) in the WordPress admin.",500,2549,100,"2025-09-02T13:04:00.000Z","6.8.5","5.0","7.4",[19,73,20,52,74],"admin","layout-preview","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fflexible-layout-preview-image-for-acf.1.4.2.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":67,"downloaded":84,"rating":67,"num_ratings":31,"last_updated":85,"tested_up_to":86,"requires_at_least":49,"requires_php":50,"tags":87,"homepage":89,"download_link":90,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"acf-beautiful-flexible","ACF Beautiful Flexible","1.0.5","Maxime Culea","https:\u002F\u002Fprofiles.wordpress.org\u002Fmaximeculea\u002F","\u003Cp>To use ACF Beautiful Flexible, simply activate the plugin to improve the ACF flexible UI. By default, it uses random images, but the idea is to customize them by adding your own.\u003C\u002Fp>\n\u003Ch4>Image convention\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The size of image should be 366×150 or bigger 732×300.\u003C\u002Fli>\n\u003Cli>They should be named based on the flexible key (\u003Ccode>push_2_light\u003C\u002Fcode>) with no underscores but dashes (\u003Ccode>push-2-light.[extension]\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>The following extensions will be resolved in that order: \u003Ccode>.jpg\u003C\u002Fcode>, \u003Ccode>.jpeg\u003C\u002Fcode>, \u003Ccode>.png\u003C\u002Fcode> and \u003Ccode>.gif\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Where images should be situated\u003C\u002Fh4>\n\u003Cp>They should more likely be situated into your theme \u003Ccode>wp-content\\themes\\my-theme\\assets\\acf-beautiful-flexible\\\u003C\u002Fcode>. But if you have a child-theme and added images into it, these will overwrite those from parent-theme.\u003Cbr \u002F>\nThe following directories will be solved according to order: plugin’s folder, child theme’s folder, theme’s folder.\u003C\u002Fp>\n\u003Cp>Also note that you can filter this path to gather all your images into a same folder :\u003Cbr \u002F>\n    add_filter( ‘acf_beautiful_flexible.images_path’, $path );\u003C\u002Fp>\n\u003Cp>Finally, you could filter all images like this :\u003Cbr \u002F>\n    add_filter( ‘acf_beautiful_flexible.images’, $images );\u003C\u002Fp>\n\u003Ch4>About ACF Beautiful Flexible\u003C\u002Fh4>\n\u003Cp>I, \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002FMaximeCulea\" rel=\"nofollow ugc\">Maxime Culea\u003C\u002Fa>, have created this plugin which I only maintain. I do not guarantee some free support. Also, thank others listed in the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMaximeCulea\u002Facf-beautiful-flexible\u002Fblob\u002Fmain\u002FCREDITS.md\" rel=\"nofollow ugc\">credits\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Consider reporting an \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Facf-beautiful-flexible\u002F\" rel=\"ugc\">issue\u003C\u002Fa> and be patient.\u003Cbr \u002F>\nAny code suggestions? I am on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmaximeculea\u002Facf-beautiful-flexible\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> as well!\u003C\u002Fp>\n","ACF Beautiful Flexible: Transform ACF's flexible layouts list into a beautiful popup.",2129,"2022-09-02T17:35:00.000Z","5.9.13",[19,88,20,22,23],"acf-addon","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-beautiful-flexible","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-beautiful-flexible.1.0.5.zip",{"slug":92,"name":93,"version":94,"author":95,"author_profile":96,"description":97,"short_description":98,"active_installs":11,"downloaded":99,"rating":13,"num_ratings":13,"last_updated":100,"tested_up_to":69,"requires_at_least":101,"requires_php":71,"tags":102,"homepage":17,"download_link":105,"security_score":67,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"auto-collapse-for-flexible-fields","Auto Collapse for Flexible Fields","1.1.0","Netgenerator GmbH Webdesign Berlin","https:\u002F\u002Fprofiles.wordpress.org\u002Fnetgeneratorgmbh\u002F","\u003Cp>By default, ACF Flexible Content fields are expanded when you load an edit screen in the WordPress admin. This can lead to a cluttered interface and excessive scrolling, especially on pages with many complex layouts.\u003C\u002Fp>\n\u003Cp>This plugin solves that problem with a simple, lightweight solution. It automatically collapses all Flexible Content layouts upon page load, giving content editors a clean and organized overview. Editors can then expand only the specific layouts they need to work on.\u003C\u002Fp>\n\u003Cp>This is a “set it and forget it” plugin with no settings required. Simply activate it, and it works.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> This plugin requires the \u003Ca href=\"https:\u002F\u002Fwww.advancedcustomfields.com\u002Fpro\u002F\" rel=\"nofollow ugc\">Advanced Custom Fields PRO\u003C\u002Fa> plugin to be installed and active, as Flexible Content fields are a pro-only feature.\u003C\u002Fp>\n","A simple plugin to automatically collapse all Flexible Content fields on page load for a cleaner admin interface.",180,"2025-10-09T08:35:00.000Z","6.5",[19,103,20,104,52],"acf-collapse","collapse","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauto-collapse-for-flexible-fields.zip",{"slug":107,"name":108,"version":109,"author":110,"author_profile":111,"description":112,"short_description":113,"active_installs":114,"downloaded":115,"rating":33,"num_ratings":116,"last_updated":117,"tested_up_to":118,"requires_at_least":119,"requires_php":120,"tags":121,"homepage":125,"download_link":126,"security_score":67,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"acf-content-analysis-for-yoast-seo","ACF Content Analysis for Yoast SEO","3.2","Yoast","https:\u002F\u002Fprofiles.wordpress.org\u002Fyoast\u002F","\u003Cp>This plugin ensures that Yoast SEO analyzes all ACF content including Flexible Content and Repeaters.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fyoast.com\u002Fwordpress\u002Fplugins\u002F\" rel=\"nofollow ugc\">Yoast SEO for WordPress\u003C\u002Fa> content and SEO analysis does not take in to account the content of a post’s \u003Ca href=\"http:\u002F\u002Fwww.advancedcustomfields.com\u002F\" rel=\"nofollow ugc\">Advanced Custom Fields\u003C\u002Fa>. This plugin uses the plugin system of Yoast SEO for WordPress to hook into the analyser in order to add ACF content to the SEO analysis.\u003C\u002Fp>\n\u003Cp>This had previously been done by the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-seo-acf-content-analysis\u002F\" rel=\"ugc\">WordPress SEO ACF Content Analysis\u003C\u002Fa> plugin but that no longer works with Yoast 3.0. Kudos to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fryuheixys\u002F\" rel=\"nofollow ugc\">ryuheixys\u003C\u002Fa>, the author of that plugin, for the original idea.\u003C\u002Fp>\n\u003Cp>This Plugin is compatible with the free ACF 4 Version as well as with the PRO Version 5. Please be aware that it ignores Pro Add-Ons for Version 4. In that case please upgrade to ACF PRO Version 5.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>If you have issues, please \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FYoast\u002Fyoast-acf-analysis\u002Fissues\" rel=\"nofollow ugc\">submit them on GitHub\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Previously called Yoast ACF Analysis.\u003C\u002Fp>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Ch4>Remove specific field from scoring\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\blacklist_name', function ( $blacklist_name ) {\n    $blacklist_name->add( 'my-field-name' );\n    return $blacklist_name;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Remove field type from scoring\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\blacklist_type', function ( $blacklist_type ) {\n    \u002F\u002F text, image etc\n    $blacklist_type->add( 'text' );\n    $blacklist_type->add( 'image' );\n    return $blacklist_type;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Define custom field a specific heading value\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\headlines', function ( $headlines ) {\n    \u002F\u002F value from 1-6, 1=h1, 6=h6\n    $headlines['field_591eb45f2be86'] = 3;\n    return $headlines;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Change refresh rate\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\refresh_rate', function () {\n    \u002F\u002F Refresh rates in milliseconds\n    return 1000;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n","WordPress plugin that adds the content of all ACF fields to the Yoast SEO score analysis.",100000,2538123,34,"2025-12-01T18:33:00.000Z","6.9.4","6.6","7.2.5",[19,20,122,123,124],"analysis","seo","yoast","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-content-analysis-for-yoast-seo\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-content-analysis-for-yoast-seo.3.2.zip",{"attackSurface":128,"codeSignals":168,"taintFlows":193,"riskAssessment":221,"analyzedAt":233},{"hooks":129,"ajaxHandlers":164,"restRoutes":165,"shortcodes":166,"cronEvents":167,"entryPointCount":13,"unprotectedCount":13},[130,136,141,143,148,152,156,160],{"type":131,"name":132,"callback":133,"file":134,"line":135},"action","admin_notices","admin_hook_notice","acf-fcl.php",107,{"type":137,"name":138,"callback":139,"priority":11,"file":134,"line":140},"filter","acf\u002Ffields\u002Fflexible_content\u002Flayout_title","acf_fclt",108,{"type":131,"name":132,"callback":133,"file":134,"line":142},166,{"type":131,"name":144,"callback":144,"priority":145,"file":146,"line":147},"admin_menu",9,"includes\\class-menus.php",24,{"type":131,"name":149,"callback":149,"priority":32,"file":150,"line":151},"add_meta_boxes","includes\\class-meta-boxes.php",23,{"type":131,"name":153,"callback":154,"file":150,"line":155},"admin_enqueue_scripts","acf_fcl_enqueue_scripts",26,{"type":131,"name":157,"callback":158,"file":150,"line":159},"init","admin_footer_screen_id",27,{"type":137,"name":161,"callback":162,"priority":11,"file":150,"line":163},"screen_layout_columns","acf_fcl_screen_layout_column",28,[],[],[],[],{"dangerousFunctions":169,"sqlUsage":170,"outputEscaping":172,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":192},[],{"prepared":13,"raw":13,"locations":171},[],{"escaped":173,"rawEcho":145,"locations":174},6,[175,178,181,182,183,184,186,188,190],{"file":150,"line":176,"context":177},201,"raw output",{"file":179,"line":180,"context":177},"includes\\html-metabox-acf-list.php",94,{"file":179,"line":180,"context":177},{"file":179,"line":67,"context":177},{"file":179,"line":135,"context":177},{"file":179,"line":185,"context":177},109,{"file":179,"line":187,"context":177},112,{"file":179,"line":189,"context":177},115,{"file":179,"line":191,"context":177},126,[],[194,213],{"entryPoint":195,"graph":196,"unsanitizedCount":31,"severity":212},"submit_data (includes\\class-meta-boxes.php:96)",{"nodes":197,"edges":209},[198,203],{"id":199,"type":200,"label":201,"file":150,"line":202},"n0","source","$_POST",101,{"id":204,"type":205,"label":206,"file":150,"line":207,"wp_function":208},"n1","sink","update_option() [Settings Manipulation]",104,"update_option",[210],{"from":199,"to":204,"sanitized":211},false,"low",{"entryPoint":214,"graph":215,"unsanitizedCount":31,"severity":212},"\u003Cclass-meta-boxes> (includes\\class-meta-boxes.php:0)",{"nodes":216,"edges":219},[217,218],{"id":199,"type":200,"label":201,"file":150,"line":202},{"id":204,"type":205,"label":206,"file":150,"line":207,"wp_function":208},[220],{"from":199,"to":204,"sanitized":211},{"summary":222,"deductions":223},"The \"acf-flexible-content-layout-thumbnail\" plugin, version 1.0.0, exhibits a mixed security posture. On the positive side, it demonstrates good practices by having no known CVEs, no external HTTP requests, no file operations, and no SQL queries that don't use prepared statements.  The attack surface is also minimal, with zero identified entry points like AJAX handlers, REST API routes, or shortcodes, and no cron events. This suggests a generally well-contained plugin.\n\nHowever, there are significant concerns stemming from the code analysis. A notable weakness is the 60% of output that is not properly escaped, presenting a clear risk of Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is displayed without adequate sanitization. Furthermore, the taint analysis reveals two flows with unsanitized paths, indicating potential vulnerabilities where data could be manipulated in unexpected ways, although no critical or high severity issues were flagged here. The absence of nonce checks and capability checks on any potential, albeit undocumented, entry points is also a significant concern, leaving the plugin vulnerable to CSRF and unauthorized access if any internal functionality were to be exposed.\n\nConsidering the lack of historical vulnerabilities, it's difficult to infer long-term patterns. This could mean the plugin is new, has been maintained diligently, or simply hasn't been targeted or thoroughly audited. The current analysis highlights the immediate risks associated with unescaped output and unsanitized paths. While the lack of an attack surface is a strength, the unaddressed output escaping and unsanitized paths are critical weaknesses that require attention to improve the plugin's overall security.",[224,227,229,231],{"reason":225,"points":226},"Unescaped output detected (40% escaped)",8,{"reason":228,"points":173},"Taint analysis shows unsanitized paths",{"reason":230,"points":46},"Missing nonce checks",{"reason":232,"points":46},"Missing capability checks","2026-03-17T01:45:03.223Z",{"wat":235,"direct":241},{"assetPaths":236,"generatorPatterns":238,"scriptPaths":239,"versionParams":240},[237],"\u002Fwp-content\u002Fplugins\u002Facf-flexible-content-layout-thumbnail\u002Fassets\u002Fimages\u002FnoImage.png",[],[],[],{"cssClasses":242,"htmlComments":243,"htmlAttributes":244,"restEndpoints":245,"jsGlobals":246,"shortcodeOutput":248},[],[],[],[],[247],"acf_fcl",[]]