Drupal 7 - How can we debug SQL query errors - drupal-7

I am new to Drupal, and while interacting with database sometimes I get this error:
Error
The website encountered an unexpected error. Please try again later.
How do I debug this issue?
How can I can see which and what query is causing the issue?

Have a look at Drupal Devel Module. After enabling it, in the config page (Admin > Configuration > Development > Development Options) you should check the first option.
Checkbox that should be selected (sorry, mine is in Spanish!)
Then, you will see a list of queries to the database every time you load a page. The time needed to perform the query is also shown. This way you can identify which queries have a bad performance.
Hope it helps

Related

Broken index in Drupal 7 site

I added a field to a Drupal view sort (level 2) and it didn't sort. I got a missing index message when I saved the view. When I enabled the syslog module to see if I could find the problem the recent log messages does not appear in the menu nor if I try to go directly to the page. What can I do to fix this?
Fixed by installing and using db_maintenance module then running cron a few times.

Unable to add a new page in DNN9 (dotnetnuke version 9)

I installed dnn version 9. When I want to add a new page I go to the contents-> Pages-> Add page. an empty white page appears without any options to add a new page or event to cancel.
This is caused by a problem with your templates folder, either missing, or bad permissions. I'm guessing when you installed you chose the blank template?
I've got a blog post on things to try to resolve
http://www.chrishammond.com/Blog/itemId/2692/Canrsquot-add-ldquopagesrdquo-in-DNN9
"If you are having problems adding Pages in DNN 9, read this blog post.
I recently upgraded all of my sites to DNN 9, the most recent one being upgraded last night. This morning I wake up to an email from a client of mine reporting a problem with adding pages in one of their sites that they also upgraded to DNN recently. I read through their email, and decide that I’ll look into their issue a bit later, have an itch to scratch on one of my own websites, so I’ll get to them later (sorry client).
Working on this site that I upgrade last night, I decided I wanted to add another page to the site, low and behold, I was unable to do so.
To add a page in DNN9 you click on the “Content” option in the persona bar, and then the Pages option. There you will be presented with a view similar to this:
image
When I clicked on Add Page there, the screen went blank, like so:
image
That’s not very useful, actually that is as far from useful as possible. Once that happens, you can’t actually “do” anything from an Admin perspective. You have to “leave” this page, go somewhere else (click on manage/users for example, then you might need to click BACK in your browser a bunch of times) then you can click on Content/Pages again to get back into the Page listing for a site.
So why is the persona bar page blank? This error is the cause:
GET https://SOMEPORTALALIASHERE/API/PersonaBar/Pages/GetDefaultSettings? 500 (Internal Server Error)
If you dig into the DNN Error Log (Admin Logs) a bit you might find a more detailed error, something along the lines of
Message:Value cannot be null. Parameter name: source
StackTrace:
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate) at Dnn.PersonaBar.Pages.Components.TemplateController.GetDefaultTemplateId(IEnumerable`1 templates) at Dnn.PersonaBar.Pages.Components.PagesControllerImpl.GetDefaultSettings() at Dnn.PersonaBar.Pages.Services.PagesController.GetDefaultSettings() at lambda_method(Closure , Object , Object[] ) at
So what does that message tell you? Well something is happening with your DNN Install trying to get a list of “page templates”. In digging further, on my site, I found the issue to be the File Permissions on the Templates folder in the portals/0/ directory. For some reason on the site that I upgraded last night, my permissions were set to ALL USERS DENY on the “Browse Files in Folder” and “Open Files in Folder” check boxes.
image
Unchecking those, clicking SAVE resolved my “pages” persona bar issues. How did those permissions get set? Who knows, this DNN site has been around since 2008 or earlier, and that never caused a problem.
There are definitely some “kinks” to be worked out of DNN9, but so far I am digging the new experience.
Regarding my “client”’s site, they had a similar, but different issue. In their case, the TEMPLATES folder didn’t exist in the Portal that they were trying to use. Simply creating a new Templates folder in their File Manager fixed that problem for their site."
I tried out many solutions but finally I figure it out by reinstalling and add Object Qualifier. because it is optional field I leave it without any value in my first installation
This error was fixed in DNN 9.0.1

Drupal 7 - Cannot delete content

This is rather odd: I am suddenly unable to delete content from my Drupal 7 website.
I can no longer delete any content, regardless of the content type. When I click delete and confirm, I return to the content overview, but the items are still there (and accessible). No errors, no warnings, no error logs. Flushing the cache does not help. I'm logged in as admin, so I cannot be a permission-issue. The url aliases however are deleted, the nodes themselves not.
I haven't done any core hacking, or installed weird modules, it's a rather basic Drupal installation. Any thoughts on how to delete content again, or how I can try to figure out what's happening here? Much appreciated!
I had this same issue. I checked the 'error log' and saw a possible conflict with the "Heartbeat Plugin" part of the "Heartbeat" module. As soon as I turned that plugin off (via the "modules" section), the issue was resolved.

DTM connectivity to SiteCatalyst

I am trying to setup DTM to report to Adobe analytics. I have pasted the header/footer code on my page and I see in fiddler that the "page load" and field level tracking is triggering DTM scripts. But I am unable to see anything in my report suite on Site catalyst.
As per DTM documentation, I have altered the AppMeasurement.js to have the report suite ID
var s = new AppMeasurement();
s.account = "myreportsuiteidonsitecatalyst";
/*
============== DO NOT ALTER ANYTHING BELOW THIS LINE ! ===============
Am I missing anything? Please help.
There's most likely an error in your DTM code. You can use the Chrome extension here to troubleshoot your DTM configuration: http://help-forums.adobe.com/content/adobeforums/en/marketing-cloud-forum/adobe-marketing-cloud.topic.html/forum__lkzf-_dtm_switchdt.html.
In addition, there are fantastic videos here which walk you through the setup of DTM and the configuration of the Analytics tool within DTM: https://outv.omniture.com/ (under Dynamic Tag Management)
You also have to have the tracking server information set either in the code editor window or the UI.
This is the problem even I was facing too.
I have analyzed this problem and get something which is very helpful but not able how to rectify this problem.
As you know sitecatalyst set s_vi cookie in our browser which is persistent, with help of this cookie we came to know that reports are reflecting in sitecatalyst reports. But while using DTM s_vi is not getting set in browser and hences no reflection of reprts in sitecatalyst.
I run my pages in Chrome and found that no cookie is being set in that browser but while using IE s_fid is being created subsitute of s_vi when s_vi not able to create.
So something wrong is with this.
you can check your cookie like _satellite.readcookie('s_vi') or _satellite.readcookie('s_fid')

Scary looking warning: Warning: Attempt to assign property of non-object in ctools_block_content_type_render()

I keep getting this warning when I update a view in a panel (I used the Views and Panel modules to create a custom home-page design). We are building an intranet for our company and our IT department has linked our SharePoint network credentials to the Drupal site using LDAP (if this would explain the warning at all). Below is a screenshot, please advise!
The accepted answer is outdated -- see the hilariously-frustrated response by dddave to the users who keep trying to apply a patch that's already been committed.
http://drupal.org/node/1739718#comment-6613292
The updated answer is to download the latest -dev version of CTools, which has the proper patch already rolled into it.
A quick search of the Drupal forum shows that your Drupal version may just need a patch:
http://drupal.org/node/1739718
What version are you running? And did this error only appear after Drupal was linked to use LDAP/Sharepoint credentials? (ie - what was the triggering event? Has this been happening for a while? Did you update Drupal recently? Or are you brand new to this role and so seeing this for the first time?)

Resources