Working with Drupal 4.7b2 and Dashboard 4.7.0.

If I put HTML (or just plain text) into any of the fields in the dashboard the text will be saved to the database and re-displayed on the page and when editing.

However, if I add php content (between tags) in any of the dashboard areas the code is initially saved to the DB and will display on the page. But, if I then edit the dashboard created node, the php content does not get displayed in the field for editing and if you save it will lose he original content.

Comments

gmak’s picture

Status: Active » Closed (fixed)

I don't know what the cause, but I've determined that it is not a bug in Dashboard, but something in my installation/configuration. Please disregard this issue

icenogle’s picture

Status: Closed (fixed) » Active

I'm having all of the problems mentioned in this bug. Not only is PHP not executed, it won't save. HTML won't save either. I can preview it and everything works properly, but when I submit it, it's as though I made no changes at all.

I have been having this problem for several days now, and I'm at my wits' end.

There are no errors in my Apache error log when this happens. Here is the access log:

192.168.0.5 - - [05/Jan/2006:13:06:01 -0500] "POST /node/1/edit HTTP/1.1" 302 -
192.168.0.5 - - [05/Jan/2006:13:06:02 -0500] "GET /node/1 HTTP/1.1" 200 4402

I would like to understand how the original submitter of this bug determined that it is related to his installation, and not a bug in the code, and whether he was able to resolve it before closing the bug?

gmak’s picture

I figured out it was the drupal installation because it was happening in any node, story, page, etc. where I had inputted php. The only way that I was able to resolve the issue was to clear everything out and reinstall from scratch. Luckily, this is only a test site that I'm trying out drupal 4.7, so it was not a mission critical issue.

Hope you are able to resolve the problem. Let me know if you find a way out other than reinstallation.

icenogle’s picture

Status: Active » Closed (fixed)

okay, that's a little different. PHP is working to display a block of teasers, but when I try to fetch that block in a dashboard with code like this, it doesn't do anything, and doesn't save:

<?php
  print dashboard_get_block( 'block', 1 );
?>

The darndest thing is that it previews just fine.

Since it's a different bug, I'll go ahead and close this one.

gmak’s picture

Status: Closed (fixed) » Active

I'm re-opening this one, as it has turned out to be a recurring problem with Dashboard and not with my setup. Each time I install Dashboard, I can save one set of PHP snippets into the dashboard areas, but if you try to edit them you get (at best) fragments of the original php. It seems as if there is something in Dashboard which is not retrieving the php correctly from the database.

merlinofchaos’s picture

I am completely unable to duplicate this problem. My feeling is that there is something complex going on inside Drupal; dashboard's load/save mechanism is extremely simple and I can't figure out how it might possibly be failing.

Would it be possible for either of you experiencing this to set up a bare system that is just Drupal and the dashboard module and reproduce this bug? And if you can, install the devel module and give me admin access to the test installation? Then I can do some fiddling and maybe get a better look at what's going wrong.

gmak’s picture

I've not been able to setup a test site, but I think I've found something. I am using TinyMCE as the WYSIWYG editor on my site. If I disable TinyMCE for Dashboard, it seems that everything in Dashboard is working. It would be interesting to find out if the other person having the problem is also using TinyMCE.

merlinofchaos’s picture

Now that is an interesting revelation.

Can you disable TinyMCE for the dashboard type? It seems to me that TinyMCE might not get along well with the ... syntax, given what it does.

gmak’s picture

You can disable TinyMCE for specific textareas. In the tinymce.module file (around line 285) you can hardcode textareas to either have 'simple' editor displayed or no editor displayed. So, I just added the following:

case 'dashboard_top':
case 'dashboard_left':
case 'dashboard_right':
case 'dashboard_bottom':

Now dashboard seems to work OK.

merlinofchaos’s picture

Status: Active » Fixed

Sounds fixed to me.

Anonymous’s picture

Status: Fixed » Closed (fixed)