When uploading such a zip file to a WordPress installation, the result is the same as when uploading the original zip file (WordPress seems to handle that automatically). When extracting locally into the file system, I end up with a different folder structure compared to when extracitng original plugin files.
]]>First of all, awesome plugin, use it every day in my workjob
An annoying issue i’ve found is that QM is spamming my debug.log with this when i go to the frontend:
[31-Aug-2024 00:51:38 UTC] PHP Warning: Undefined array key "C:/laragon_new/www/XXX/wp-content/themes/XXX/parts/header.html" in C:\laragon_new\www\XXX\wp-content\plugins\query-monitor\output\html\theme.php on line 163
[31-Aug-2024 00:51:38 UTC] PHP Warning: Undefined array key "C:/laragon_new/www/XXX/wp-content/themes/XXX/parts/footer.html" in C:\laragon_new\www\XXX\wp-content\plugins\query-monitor\output\html\theme.php on line 163
For info, i use PHP 8.3 at the moment but i don’t think (not quite sure) that’s it’s related.
What i found out is that QM seems to be collecting data differently about “paths” on Windows (which is causing the PHP Warnings.
When i log $parts and $data->count_template_parts, i can clearly see that one is using forward slashes but the other one is using a mix, the logs:
[31-Aug-2024 00:59:27 UTC] DEBUG: $parts Array
(
[C:/laragon_new/www/XXX/wp-content/themes/XXX/parts/header.html] => parts/header.html
[C:/laragon_new/www/XXX/wp-content/themes/XXX/parts/footer.html] => parts/footer.html
)
[31-Aug-2024 00:59:27 UTC] DEBUG: $data->count_template_parts Array
(
[C:\laragon_new\www\XXX/wp-content/themes/XXX/parts/header.html] => 1
[C:\laragon_new\www\XXX/wp-content/themes/XXX/parts/footer.html] => 1
)
If you have an idea on how to fix this, that would be great
Have a good day,
Damien
Today I did update to Calendar 6.5.1 as usual and after that new version of calendar is broken 
It looks like CSS is broken not only what is presented on the website but even settings page is broken and not well displayed?
Any idea why? Somebody has similar issue?
Link to image how the setting page looks: https://ibb.co/nM8bVTv
]]>Uploads directory not writable?— the following directory is not writable:?/home/a5qls5gso4h7/public_html/[redacted]/wp-content/uploads. Update the file permissions for this folder to enable backups and export migrations.
But a5qls5gso4h7 is not the directory of the site. The Diagnostic Info & Error Log knows this, it shows the correct one in site_path and elsewhere. The actual uploads directory has the correct permissions.
Any suggestions? Thanks in advance.
]]>but when I create the po file in author path, it’s not working,
if I change the file path to System or Custom ptah, than the translate is working,
why will this happen? and hope someone can help me, I want the translate file in author path than when I install the plugin to my other site can have the translate.
]]>I am trying to update my templates like so:
Copy the default template from?
Woowp-content/plugins/woocommerce/templates/[path-to-the-template]?and paste it in your theme folder found at?wp-content/themes/[path-to-theme].
However, some of my outdated templates are not in the location you refer to but at these links:
/my-awesome-site/public_html/wp-content/plugins/woo-gutenberg-products-block/templates/notices/error.php?version?3.9.0?is out of date. The core version is 8.6.0,/?version?3.9.0?is out of date. The core version is 8.6.0,my-awesome-site/public_html/wp-content/plugins/woo-gutenberg-products-block/templates/notices/notice.php/?version?3.9.0?is out of date. The core version is 8.6.0,my-awesome-site/public_html/wp-content/plugins/woo-gutenberg-products-block/templates/notices/success.phptwentytwentyfour/woocommerce/single-product/tabs/tabs.php?version?–?is out of date. The core version is 3.8.0
The path within Twenty Twenty 4 puzzle me. Do I drop templates
- within root of theme as you have specified above
- within the template folder of the theme
- in an exact structure matching the location within woo but then inside theme?