MIGX TV broken (after update to 2.9.3-pl?)

134 Posts

itWillBeOk Reply #1, 11 years, 4 months ago

Hi,
I have an existing website with several MIGX TVs, all working fine. But now I noticed, that in one TV I can't edit rows anymore, nor delete them. I did not touch the config. I created a new TV since the other last worked, but I guess that should not interfere? I did update to 2.9.3-pl though.

Error in dev tools when trying to edit:

Uncaught TypeError: Cannot read property 'data' of undefined
?a=resource/update&id=135:1342

When trying to remove, the remove? dialog appears, but then nothing. No error either.

This is my columns config:

[  
   {  
      "MIGX_id":1,
      "header":"ID",
      "dataIndex":"MIGX_id",
      "width":10,
      "sortable":"false",
      "show_in_grid":1,
      "renderer":"",
      "clickaction":"",
      "selectorconfig":"",
      "renderchunktpl":"",
      "renderoptions":"[]"
   },
   {  
      "MIGX_id":2,
      "header":"Image",
      "dataIndex":"image",
      "width":200,
      "sortable":"false",
      "show_in_grid":1,
      "renderer":"this.renderImage",
      "clickaction":"",
      "selectorconfig":"",
      "renderchunktpl":"",
      "renderoptions":"[]"
   },
   {  
      "MIGX_id":3,
      "header":"ALT Text",
      "dataIndex":"de-textAlt",
      "width":"",
      "sortable":"false",
      "show_in_grid":1,
      "renderer":"",
      "clickaction":"",
      "selectorconfig":"",
      "renderchunktpl":"",
      "renderoptions":"[]"
   },
   {  
      "MIGX_id":4,
      "header":"* Credits",
      "dataIndex":"de-textCredits",
      "width":"",
      "sortable":"false",
      "show_in_grid":1,
      "renderer":"",
      "clickaction":"",
      "selectorconfig":"",
      "renderchunktpl":"",
      "renderoptions":"[]"
   },
   {  
      "MIGX_id":5,
      "header":"* Description",
      "dataIndex":"de-textDescription",
      "width":"",
      "sortable":"false",
      "show_in_grid":1,
      "renderer":"",
      "clickaction":"",
      "selectorconfig":"",
      "renderchunktpl":"",
      "renderoptions":"[]"
   }
]

Any ideas?

This question has been answered by itWillBeOk. See the first response.

@itWilllBeOK

☆ A M B ☆
24,524 Posts

sottwell Reply #2, 11 years, 4 months ago

A couple of times I've had TVs get locked up, and I couldn't even successfully remove the offending TV until I had moved every resource using it off of its template, and remove the template as well. Not even removing the TV from the template access helped. I had to delete the template altogether, then create a new one for the resources, and a new TV.

The first time, I was able to delete the TV, but it just gave me a white-page if I tried to edit a resource that had been using the TV. I even enlisted MODX help, and they couldn't figure out what went wrong either. Fortunately it was on the MODX Cloud, and I was able to restore from the latest backup and be back in business again.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

134 Posts

itWillBeOk Reply #3, 11 years, 4 months ago

Thanks Susan.
That does not sound very encouraging...

I will wait if Bruno has some magic trick up his sleeve. If not I will just tell the client it is their fault and all is working fine on my end.
(Just kidding)

@itWilllBeOK

5,888 Posts

Bruno17 Reply #4, 11 years, 4 months ago

Could you try the same configuration at a fresh MODX and with a fresh install of that MIGX-Version?

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

discuss.answer

134 Posts

itWillBeOk Reply #5, 11 years, 4 months ago

Hi Bruno,
seems like I just found the problem:
under contextmenues I had checked 'update' and 'remove'. I unchecked those and checked 'update_migx' and 'remove_migx'.
Working fine now.

But it did work for about year until now. I swear!

@itWilllBeOK

5,888 Posts

Bruno17 Reply #6, 11 years, 4 months ago

I see.
I think, the context-menues for the MIGX-grid was hardcoded before and you couln't choose your own context-menue-items.
Since you can select them now, you need to choose the migx-specific items.
The other ones are for MIGXdb.

If you select none, you will get the default context-menue-items

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

134 Posts

itWillBeOk Reply #7, 11 years, 4 months ago

Working fine now. Like smeared, as ze germans like to say.

@itWilllBeOK

65 Posts

chrisissorry Reply #8, 11 years ago

Thanks itWillBeOk, you saved my day! I was already mentally preparing for reinstalling the whole system. You solution worked right away!

134 Posts

itWillBeOk Reply #9, 11 years ago

It's the little things...

@itWilllBeOK

Answered MIGX TV broken (after update to 2.9.3-pl?)