The list you are referring to was done start to mid 2013, which can be a bit outdated as the was major improvements/new feutures like The TINYMCE editor undergone major modifications and upgrades as from version 3.9 Version 4 saw the introduction of new shortcodes like the video shortcode and audio playlist, just to name … Read more
If it’s just for your understanding, then install the Query Monitor plugin, which gives you a lot of information about what’s going on under the hood
You have to register the menu, as you have done, and then use the function wp_nav_menu() in the template file where you want to display the menu. wp_nav_menu( array( ‘theme_location’ => ‘footer_menu’, );
If I understand you correctly, this is because you have a index.html (from your static site) and a index.php (from WordPress). So if you rename your index.html to something like: oldindex.html, the correct index.php will be shown (the WordPress index.php). Alternatively, you could remove the index.html.
That’s a PHP warning, not technically an error, and isn’t real critical. It’s due to your webhost updating the version of PHP; and the theme StandardTheme_272 should initialize an object before setting a property. See if there is a theme update. If not, https://stackoverflow.com/questions/14806959/how-to-fix-creating-default-object-from-empty-value-warning-in-php for instructions on how to fix the theme. You can temporarily … Read more
Could be a few things causing it. Have you altered any core files or wp-config in anyway? Are the themes definitely valid, they have a style.css file with the required information filled in? I’d recommend setting up a completely fresh WordPress installation. Copy each theme in one at a time and make sure they show … Read more
Problem was, that the FTP user does not equal the Apache / webserver user. I just had to (recursively) own the wordpress directory /var/www for the www-data/webserver user: sudo chown -R www-data:www-data /var/www Please refer to this link for further info about the owner of a directory.
The simplest would be to add it to a CSS style. WP output body classes, which allow to precisely target any specific page with CSS by ID, for example: <body class=”page page-id-7 page-template-default logged-in admin-bar no-customize-support group-blog no-sidebar”> While it’s not default I also like to hook into it and add page-[name] class for myself. … Read more
It’s look like fontawesome fonts are not available. In the fontawesome.css the path is ../fonts/fontawesome-webfont.eot Verify this path, correct it if fonts are another folder. The css is waiting for this structure —theme fonts fontawesome-webfont.eot … css fontawesome.css … But your structure is maybe — theme fontawesome.css fonts fontawesome-webfont.eot …
…if it’s a good practice to load the main theme styles this way, since usually they’re hardcoded into the header before anything else. Long story short, yes. WordPress advocates the enqueue “API” for all assets whenever possible.