Resolved – Error 495 in Drupal – panels_renderer_standard.class.php

Notice: Undefined index: settings in panels_renderer_standard->render_pane() line 495 panels_renderer_standard.class.php). this is the original error. this is my contribution to the issue on

Posted by pjmcghee on October 23, 2013 at 8:46am new

Hey, I was able to resolve this error pretty easily. I had been working with some new styles, making a clone of an existing, changing styles around on a specific panel pane. then, i decided that i really needed to make the change to the entire column. so i added a style there and changed the panel pane style back to the original style. i then began receiving the error.

I was quite sure what was going on after reading this post (and thanks @merlinofchaos! for everything!). I recreated the offending, or broken panel pane to make sure it worked properly, deleted the original pane and saved the page. the error is now gone.

then, i added the original style to the new, recreated pane. now, all is correct and the error is gone. and i have the new style on the column so that i can style the whole thing the way that works best for me.

so there never was actually an empty style, i believe that the system just got a little confused with the multiple changes. that also seems to be consistent with some drupal panel behavior. sometimes you just need to delete and recreate rather than fix unless you want to really dig into the db. and i really don’t!

small price to pay for the amazing panels module. @merlinofchaos – you rock.

Undefined index: settings in panels_renderer_standard->render_pane() (line 495

I received this error after adding a content pane to a panel page. It really didn’t make much sense, looked like it might be related to a malformed machine name. – here is some info about the error in general.

what i did to fix it was remove the last Views Content Pane that I had added and saved. The error disappeared.

I opened the View itself and saved that without making any changes and was able to readd the pane to the page and viola! no more error. Very odd….

Tab Tamer – Error from Node add/edit when using Panels and Variants

tab tamer is a great module. all the default drupal tabs along the top really throw off my css. so i found this great mod to help. tab tamer allows you very granular control over the system generated tabs.

When I chose “hidden” for the tab in tab tamer for the node/edit field the variant for node add/edit disabled itself. after testing a few things, i was able to get it working again by setting that specific tab to hidden.

Error from Link Module – line 1305 link.module

I have been getting this error when I save fields to a content type that I have created. Here is the error.

Notice: Undefined index: title_value in link_field_update_instance() (line 1305 of /var/www/foo/public/sites/all/modules/link/link.module) – note the path may not be the same for you.

Here is the issue summary:

There is a patch listed here. very easy to install manually. and fixed the issue.

Rich Text Editors in Drupal

Ug. This has been a real pain. But I believe that I finally have things sorted out. To get CKEditor working, and I mean really working in Drupal, I uninstalled the WYSIWYG mod and started over.

  • I installed the actual CKEditor module from
  • I reinstalled the ckeditor library into sites/all/libraries
  • i changed the content types to use the new editor
  • i moved the iframe plugin library to the ckeditor/plugins folder
  • i enabled the now-present iframe option in the ckeditor setup

there were still errors present in the CKEditor version from WYSIWYG. i think that WYSIWYG just has issues. I’m sure that there are ways to work around them but this is working for me and there are no errors. Much Better.

CKEditor could not be detected – resolution

Well, I had trouble installing the CKEditor so I went with TinyMCE. But I began to get errors from that as well. And I don’t really like using a solution because I didn’t take the time to figure out what was wrong. So I went back and made CKEditor work. There is a patch for those of you using WYSIWYG 7.x-2.0 and CKEDITOR 7.x. You may receive an error that CKEditor cannot be detected.  This fixed it for me in sand and prod.

Here’s another Patch

Posted by sakseiw on December 5, 2012 at 1:50pm

In …/modules/wysiwyg/editors/ change line from function wysiwyg_ckeditor_version($editor)

if (preg_match(‘@version:'(?:CKEditor )?([d.]+)(?:.+revision:'([d]+))?@’, $line, $version)) {


if (preg_match(‘@version:”(?:CKEditor )?([d.]+)(?:.+revision:”([d]+))?@’, $line, $version)) {

This changes version number search from single quotes version: ‘4.0’ to double quotes version “4.0”

It worked for me on Drupal 7.17 and wysiwyg 7.x-2.2

translation management module

I had to take this part of multilingual out. i don’t need it because of the way that I am approaching all this and worse, it was giving me major errors from a bunch of different things. menus (list links specifically) in particular. so i ripped it out.

the errors are the annoying 500 errors from sql that don’t tell you too much. but there were other errors as well. i don’t need this anyway. i have to keep moving ahead and i don’t have time to figure out errors from something that i don’t really need anyway.

be careful with multilingual. if you read up, you’ll see that multilingual is one of the centerpieces of drupal 8. but 8 will be a while and i can’t wait. but there are simply so many modules in 7 that you have to enable that it is not too surprising that there are complications.

Error with the Core Contact Form and Google Analytics Tokenizer

well, today I enabled the user contact form and tested it. The form works but I received an error from PHP about a deprecated function. Here is the link to the fix:

To be honest, I’ve had more luck installing these patches manually than using the patch application from the command line. I might be doing something wrong but I don’t think so. I believe that what is happening is that the patch is issued for a version of the module, at a specific line number. Then, the module is changed and the line number changes but the patch isn’t necessarily committed to the module. So the line numbers no long match. Or, I am an idiot who doesn’t know what he is doing.

So i usually open the patch, check out what is being changed and add it manually with Aptana. that way i have to look at the code too.

Error from CTools in Panels during preview

I got a bunch of errors from the preview feature of panels via page manager.

go to the ctool module dir from a terminal window and type –

curl | git apply

i had to install git to make this work (yum install git) and i received an error about an unexpected difference in file sizes but it looks like the patch worked. known issue. i wanted to document it because i’ll probably have to put this into prod as well as sand.

Resolved – Warning: Parameter 1 to icl_content_node_view

I have been working with a bunch of the language modules and I am now receiving this error on the main page of my quality environment. Eh, that’s why you have quality. Well, that’s really why you have a sandbox. but my sandbox really needs some help. Fortunately, I backed everything up before my last prod change, including quality. If I can’t fix it, I may roll back and punt.

Warning: Parameter 1 to icl_content_node_view() expected to be a reference, value given in module_invoke_all() (line 857 of/var/www/html/includes/

this is a known bug. and

Here is the actual patch procedure from hgneng. Big thanks for this; it worked perfectly.

I did have to install the app “patch” to use this proc. simple – yum install patch

Posted by hgneng on May 16, 2012 at 8:38am

The patch works for Drupal 7.14. Why not merge it to dev?

@tzanis how to install patch (for Linux user):
$ cd sites/all/modules/translation_management/icl_content
$ wget…
$ cp
$ patch -p1 -i translation_management-node-hooks-by-value.patch.txt