Fatal Error WP- prefix
-
Hi! There is an error in your plugin, specifically you are using a hard-coded path to the wp-content directory, which doesn’t always have the ‘wp-‘ prefix, and this causes the issue. I recommend you use a different method to determine the path to wp-content, because not everyone has it as ‘wp-‘, it could be ‘content’, ‘media’, ‘base’, or ‘site’; in my case, it’s ‘site’. That’s why the constant ‘IGD_CACHE_DIR’ is not defined correctly because you are using a hard-coded path like this: define( ‘IGD_CACHE_DIR’, ABSPATH . ‘wp-content/integrate-google-drive-cache’ ); instead of a dynamic one. I recommend defining it correctly, for example:
// Get the path to the content directory
$content_dir = WP_CONTENT_DIR;
// Define the cache directory path by appending your cache folder name
define( 'IGD_CACHE_DIR', $content_dir . '/integrate-google-drive-cache' );
// Get the cache URL by appending the cache folder name to the content URL
define( 'IGD_CACHE_URL', content_url() . '/integrate-google-drive-cache' );Sure! Here’s a more concise and clear recommendation in English for the plugin developer:
Recommendation for Developer:
To make the plugin compatible with custom content ‘WP_CONTENT_FOLDERNAME’ folder names (e.g.,
my_new_pathinstead ofwp-content), use the dynamic WordPress constantsWP_CONTENT_DIRandWP_CONTENT_URLinstead of hardcoding paths. This ensures the plugin works correctly regardless of the content folder name.Here’s how to update the code:
define( 'IGD_CACHE_DIR', WP_CONTENT_DIR . '/integrate-google-drive-cache' ); define( 'IGD_CACHE_URL', WP_CONTENT_URL . '/integrate-google-drive-cache' );This approach adapts to any changes in the content folder name, providing better flexibility and compatibility.
PS> I think need use WP_CONTENT_DIR /cache/integrate-google-drive correct folder )
define( ‘IGD_CACHE_DIR’, WP_CONTENT_DIR . ‘/cache/integrate-google-drive’ );
define( ‘IGD_CACHE_URL’, WP_CONTENT_URL . ‘/cache/integrate-google-drive’ );
-
Hi @power2009,
First, we sincerely apologize for any inconvenience caused by our plugin or support.
Regarding your suggestion to update our plugin’s code using internal WordPress core constants, we appreciate your input. However, the WordPress plugin review team strongly advises against using internal constants. Instead, they recommend using functions to maintain better compatibility and adhere to best practices. For this reason, we’ve implemented functions to determine cache directory locations.
Here is a reference:## Determine files and directories locations correctly
WordPress provides several functions for easily determining where a given file or directory lives.
We detected that the way your plugin references some files, directories and/or URLs may not work with all WordPress setups. This happens because there are hardcoded references or you are using the WordPress internal constants.
Let’s improve it, please check out the following documentation:
https://developer.ww.wp.xz.cn/plugins/plugin-basics/determining-plugin-and-content-directories/It contains all the functions available to determine locations correctly.
Most common cases in plugins can be solved using the following functions:- For where your plugin is located:
plugin_dir_path(),plugin_dir_url(),plugins_url() - For the uploads directory:
wp_upload_dir()(Note: If you need to write files, please do so in a folder in the uploads directory, not in your plugin directories).
Example(s) from your plugin:
integrate-google-drive.php:29 define( ‘IGD_CACHE_DIR’, WP_CONTENT_DIR . ‘/integrate-google-drive-cache’ ); —–> WP_CONTENT_DIRAdditionally, thank you for bringing to our attention the conflict with PHP v8.4 compatibility in the Google Drive PHP SDK. We are actively investigating the issue and will release an update shortly to address this compatibility problem.
Thank you for your understanding and support!
- For where your plugin is located:
The topic ‘Fatal Error WP- prefix’ is closed to new replies.
