Limited Editor role

76 Posts

twz-17 Reply #31, 16 years, 10 months ago

Locate this file:
/manager/actions/mutate_content.dynamic.php
and open it in a text editor

About 3/4 through the file (at line 873) you will find this line

<?php } ?>

replace that line with these:

<?php } else {
                echo <<<HIDDEN
            <tr>
              <td class="hide3" colspan="2">
                    <input type="hidden" name="type" value="{$content['type']}" />
                    <input type="hidden" name="contentType" value="{$content['contentType']}" />
                    <input type="hidden" name="content_dispo" value="{$content['content_dispo']}" />
              </td>
            </tr>
HIDDEN;
                      } ?>

then save/upload the file again.

718 Posts

Paprikas Reply #32, 16 years, 10 months ago

Or download whole file from repository.
http://svn.modxcms.com/svn/tattoo/tattoo/branches/1.0.x/manager/actions/mutate_content.dynamic.php

277 Posts

bbeer Reply #33, 16 years, 10 months ago

Thanks a lot guys

you just saved my evening.

171 Posts

etal Reply #34, 16 years, 10 months ago

A different bug but seems related.

I replaced the mutate_content.dynamic.php file with the one from svn and now when a new document is created everything looks fine in the manager backend but in the front end you see the following error on the top of the content section of the document:

Warning: Unterminated comment starting line 1 in /public_html/manager/includes/document.parser.class.inc.php(770) : eval()'d code on line 1

Has anyone seen this? How do I fix it?

171 Posts

etal Reply #35, 16 years, 10 months ago

Resolved.

Somehow the update messed with one of the snippets (AuthorTime), very strange.

5 Posts

strillogy Reply #36, 16 years, 10 months ago

I have the same problem--if a editor changes something in a page, the resource content disappears. I tried removing the resource and adding a brand new one, but that just caused more problems.

☆ A M B ☆
237 Posts

mdsdesign Reply #37, 16 years, 10 months ago

Solved: I found what I needed to change in the database: document and text/html... just matched what the other files showed. Worked fine as did the patch or file fix. Seems to be working on both of my 1.0.1 installs. However, I just launched a site with 1.0 and I’m thinking about waiting for the next release before upgrading. I don’t need any more "Mystery Bugs" showing up just as a launch a site for a new client.

Thank goodness for this forum and great community!

Quote from: jeremy at Oct 30, 2009, 11:07 AM

Bring up the database and edit the modx_site_content table

Find the row for the document that is not working and edit the "type" and "contentType" fields back to what they should be.

Can you explain: back to what they should be? What should they be? Sorry, a designer here and this is all new to me.

Michael Smull
http://www.bigpixelstudio.com
twitter: @mdsdesign

76 Posts

twz-17 Reply #38, 16 years, 10 months ago

type is usually "document" and contentType is "text/html" (without the quotes)

5 Posts

strillogy Reply #39, 16 years, 10 months ago

the patch worked!

☆ A M B ☆
237 Posts

mdsdesign Reply #40, 16 years, 10 months ago

Can I ask a stupid question? Why isn’t the patch just added to the current download of 1.0.1?

It fixed the problem on both of my sites. Why do we need to wait for 1.0.2 for this to be added?

Just wondering. It would save a lot of people a lot of time and effort....

Michael Smull
http://www.bigpixelstudio.com
twitter: @mdsdesign