{"id":140,"date":"2014-07-30T16:34:13","date_gmt":"2014-07-30T16:34:13","guid":{"rendered":"http:\/\/www.ahosting.net\/blog\/?p=140"},"modified":"2014-07-30T16:35:55","modified_gmt":"2014-07-30T16:35:55","slug":"troubleshooting-some-of-the-most-common-issues-with-drupal","status":"publish","type":"post","link":"https:\/\/www.ahosting.net\/blog\/troubleshooting-some-of-the-most-common-issues-with-drupal\/","title":{"rendered":"Troubleshooting Some Of The Most Common Issues With Drupal"},"content":{"rendered":"<p>Drupal is a powerful tool in the right hands, but like any content management system, it isn\u2019t perfect. Regardless of whether you\u2019re a seasoned veteran or a green newcomer to the platform, you\u2019re bound to eventually run into a problem or two you can\u2019t figure out on your own. Today, we\u2019re going to go over a few of the most common issues you\u2019re likely encounter with a Drupal installation.<\/p>\n<p>More importantly, we\u2019re going to explain how to fix them.<!--more--><\/p>\n<h2><b>A General Overview Of Drupal Troubleshooting<\/b><\/h2>\n<p>Before we start getting into specifics, I\u2019d like to offer a bit of advice, taken straight <a href=\"https:\/\/www.drupal.org\/node\/1925512\">from the Drupal home page<\/a>. It lays out a process which can be used to troubleshoot virtually any problem you might encounter with your installation. It goes as follows:<\/p>\n<p>1. Stay calm. Stop and think; ask yourself if you\u2019ve made any recent changes to your site. Have you installed or updated any modules? Are there version conflicts or errors that might be preventing your CMS from running properly? Think about the last time it worked, and work out what\u2019s changed since then.<\/p>\n<p>2. Assuming you\u2019ve got the core dblog module enabled (you should), you can find error reports under \/admin\/reports\/dblog. Check the logs and note any error messages you see. Examine also the logs of any additional non-drupal applications you\u2019re using, such as Apache or PHP.<\/p>\n<p>3. Validate your page to check for errors in the HTML markup. There are a number of plugins <a href=\"http:\/\/validator.w3.org\/\">and websites<\/a> designed to help you do this.<\/p>\n<p>4. Check your CSS for errors. In particular, you should be looking at child and container elements; these are the areas in which issues most commonly surface. Make any revisions or overrides in a new style.css file rather than your original. Again, there are a number of tools to help make this process a little easier on you, such as the <a href=\"http:\/\/chrispederick.com\/work\/webdeveloper\/\">web developer toolbar<\/a>.<\/p>\n<p>5. Clear the cache. There\u2019s a chance that it might contain a few errors, and clearing it might clear up all your problems, as well. You can do this on the Performance page by clicking the \u201cClear all caches\u201d button.<\/p>\n<p>6. Pore over the README for your module. It might contain something useful.<\/p>\n<p>7. Dive into your code and debug it to check for errors.<\/p>\n<p>8. Check your memory. If you\u2019re getting the White Screen of Death, it may be because of an error with modules or code, but there\u2019s also a good chance that you\u2019re running out of memory.<\/p>\n<p>9. When all else fails, look the error up on Google. Chances are pretty good that someone else has encountered it at some point. You\u2019d be surprised how often even the most tech savvy resort to this step.<\/p>\n<p>Alright. Now that we\u2019ve gotten that out of the way, let\u2019s look at a few errors that <b>cannot <\/b>be immediately addressed through the above steps.<\/p>\n<h2><b>Vanishing Comments<\/b><\/h2>\n<p>Has all the content on your site created by anonymous users disappeared? That\u2019s very likely due to a database issue. Go into your MySQL {users} table, and make sure you add uid=0. This will allow anonymous users to once again post and save content.<\/p>\n<h2><b>The Disappearing Images<\/b><\/h2>\n<p>Images can be a little finicky in Drupal, as well \u2013 either your CSS images disappear when caching is turned on or images within your posts are disappearing after the node they\u2019re contained by is published. In the first case, the default settings of Drupal are likely to blame. The solution will require you to grant the role of whatever user is publishing the post Full HTML access,\u201d at which point you\u2019ll also need to create a custom Input Format with the img tag.<\/p>\n<p>In the second case, the solution is a bit more involved. After first checking the permissions relative to files and CSS folders (make sure your server has read\/write access), you\u2019ll next want to examine whether or not your CSS is set up to import to another file. Check to see whether you\u2019re using relative or absolute paths, and check your URL for any out-of-place characters.<\/p>\n<h2><b>Users Can\u2019t Edit Pages (Or Can\u2019t See Their Content)<\/b><\/h2>\n<p>One of the more frustrating issues that might crop up with your Drupal installation involves user permissions. A user \u2013 even one with access privileges \u2013 may find that they are unable to edit a particular page. Thankfully, this is corrected easily enough; simply check the user\u2019s role and compare it against the input format of the body field. There\u2019s a good chance that either the user\u2019s role is misconfigured, or that it\u2019s unable to edit content of that particular breed.<\/p>\n<p>Another common problem involves how user roles interact with the cache. A user who\u2019s created content and logs out is suddenly unable to see what they created. To fix this, clear the browser cache, clear the Drupal cache, and adjust the \u201cminimum Cache lifetime\u201d under settings.<\/p>\n<h2><b>Website Load Time Issues<\/b><\/h2>\n<p>Like many content management systems, Drupal tends to get a little bloated if you don\u2019t operate it properly. If your website seems to take an age to load, it may well be because you aren\u2019t making full use of its caching capabilities. If you don\u2019t have block and page caching enabled, do so, then flush the cache. You might also consider compressing any large files your CMS is dealing with, such as CSS and Javascript.<\/p>\n<h2><b>Busted Layout<\/b><\/h2>\n<p>Occasionally, the layout of your website may seemingly \u2018break\u2019 without warning. There are a number of issues which might cause this to happen, including a messed up cache or a corrupted theme registry. To fix this, first empty your cache under the Admin\/Settings\/Performance. If that still doesn\u2019t do the trick, try rebuilding the theme registry.<\/p>\n<p>Note that this is much easier to go about if you install the Devel module; a module created specifically to streamline Drupal\u2019s development process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Drupal is a powerful tool in the right hands, but like any content management system, it isn\u2019t perfect. Regardless of whether you\u2019re a seasoned veteran or a green newcomer to the platform, you\u2019re bound to eventually run into a problem or two you can\u2019t figure out on your own. Today, we\u2019re going to go over [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":141,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[23],"tags":[],"class_list":["post-140","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-drupal"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/comments?post=140"}],"version-history":[{"count":4,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/140\/revisions"}],"predecessor-version":[{"id":145,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/140\/revisions\/145"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media\/141"}],"wp:attachment":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media?parent=140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/categories?post=140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/tags?post=140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}