It is easy to get a post ID in WordPress. To echo it on screen we write:
<?php the_ID(); ?>
To store the ID into variable we use something like this :
$id = get_the_ID();
There is one caveat though: if you read the description on WordPress codex it says this in both cases: This tag must be within The Loop.
So if you ever wanted to retrieve or display the WordPress post ID in footer or header or outside of The Loop you might end up being disappointed because the ID returned is not the correct one (usually we always get the same id, most probably the last one?)
Now I am not going to go into technical details or why is that so here is the solution that worked for me. You
$post = $wp_query->post;
There are some other ways with global variables and some other but it seem it doesn’t work for everyone. This one worked on the first try. Let me know in comments if it doesn’t work for you.
There is nothing worse than getting blank screen when developing for WordPres – also ‘officially’ known as The White Screen of Death – because you have no idea what went wrong. No errors, nothing useful, just blank screen. It’s even worse when it just appears out of nowhere. This happened to me few times in the past and then just recently. Woke up in the morning and the entire site (not this one) displayed just blank white page.
First thing you should do is rename the
plugins folder and see if it works. If yes then the problem is in one of the plugins so if your admin works start disabling plugins one by one. If admin doesn’t work then try renaming plugin folders via FTP. If this doesn’t help then rename the
themes folder and see if the problem was caused by one of your theme.
This didn’t help in my case. So I went to WordPress site (link below) and insert the code they recommended! It STILL didn’t work and there were no errors displayed! So finally I modified the code a little and finally the error appeared! I don’k know why are they posting a solution that doesn’t display the errors.
Here is the code that started showing errors and I finally able to fix it. Still the mistery remains why did the blank screen start appearing when it was working just fine yesterday when I went to bed. Ah, the ‘joys’ of developing.
wp-config.php file in the root directory of your worpress and insert this just above the
/* That's all, stop editing! Happy blogging. */ comment. Refresh the WordPress and hopefully you will see PHP error telling you what went wrong.
// Enable WP_DEBUG mode
// Enable Debug logging to the /wp-content/debug.log file
// Enable display of errors and warnings
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
After you fix the error don’t forget to remove or at least comment the added code.
In case it didn’t work, here are some more steps to try to fix it:
Common WordPress Errors and Debugging in WordPress
Seems like qTranslate is not really updated anymore or at least it is updated very slowly. So when I updated WordPress to new version I got this message and qTranslate editor in admin was disabled.
The qTranslate Editor has disabled itself because it hasn’t been tested with your WordPress version yet. This is done to prevent WordPress from malfunctioning. You can reenable it by clicking here (may cause data loss! Use at own risk!). To remove this message permanently, please update qTranslate to the corresponding version.
I guess the easiest way is to just click on the link and it will probably enable itself. I googled it and it seems some people might have problems with that. So the solution that worked for most people is this:
wp-content/plugins/qtranslate/qtranslate.php file and change line 90 from
just save it and that’s it.
Of course if WordPress is updated to new version qTranslate will disable itself again. What you can do is enable it for all version by dynamically inserting current WordPress version, like this
qTranslate will now work for all (future) versions of WordPress.
Hint: You can find out your WordPress version on the bottom right in the admin or by opening a file
/wp-includes/version.php and checking the
$wp_version variable on the top.
Note: Do this on your own risk. It seems to work for most people but beware you might loose your data if something goes wrong. The safest way is to wait for author of qTranslate to update it but it seems this is not happening.
After I resolved my speed problems with Composer (see the post here ) I got this error once the Composer ended updating dependencies:
Fatal error: Call to undefined method Illuminate\Foundation\Application::getConfigLoader() in E:\path-to-my-project\vendor\laravel\framework\src\Illuminate\Foundation\start.php on line 106
As I already mentioned in my previous post I don’t know if this was due to me canceling composer updates several times or something else but the same error appeared when I opened my project URL in web browser.
The solution is simple: Delete
After that run
php artisan optimize command, which will generate new compiled.php file. I am not sure if this last step is necessary because everything seems to work even without the compiled.php file but I would advice to run this command just in case and regenerate compiled.php file.