Hey Peter,
It's hard to say where the error has occurred exactly. I suppose you did not edit the resx files or use a foreign locale, being in Australia. That leaves the possibility that the data is in some way corrupted. I'm guessing here. I'll think this over. Can you confirm that you use the original locale (i.e. en-US)?
Peter

Peter

I did make some changes for another module that I am using to correct some spelling differences.  I added it to the language as en-au.  The default for the portal is en-au.  I probably went the wrong way about it.  Is this is what is causing error

Any suggestions

Thanks

Peter M.

Find the localization string called 'ColumnList.Text'. You won't miss it as it is the longest there. Make sure this is the same as the one in the default file. Then verify the module is working again. Then you can adapt the string as follows: only touch the red words:

FileCheckBox|Select|24|||||||;TemplateIcon||24|||||~/DesktopModules/Bring2mind/DMX/images/View.gif|Details||EntryId||EntryId=[PARAMETERS]&Command=Core_ViewDetails|False||~/|Icon16||||;Description|Description||||True|Description||||||Default|;StatusLocked||24||||||Locked|File;StatusPrivate||24||||||Private|;StatusDeleted||24||||||Deleted|;StatusApproved||24||||||Not Approved|;StatusAttention||24||||||Attention|;ActionDownload||24||||||Download|File;ActionJump||24||||||Jump|Hyperlink;ActionJumpNew||24||||||Jump in new window|Hyperlink;LastModified|Last Modified|100||{0:d}||LastModified|||;Author|Author|150||||Author|||File;DateSubmitted|Created|70||{0:d}||DateSubmitted|||;FileSize|Size|70||||FileSize|||File

Peter

 

Peter,

Thanks for that, It is now working.  All I need to do now is update on live server.  I have a follow up question.

The Columnlist.text in 3.1.4 version i was running was changed to customise the view for collections, categories and search.  We had added some custom attributes to view and removed some of the other headings.  I changed them all back to default setting and it worked.

Question is can I change them back to include some custom attributes we have added and if so will this need to be done everytime I upgrade.

Is this done the same way as written in the DMX admin manual?

Regards

Peter M

 

Peter,

Yes it is. I'm afraid the taylorability of the columns of the datagrid didn't turn out to be as easy to configure as I hoped. I will be looking for alternatives to make this easier. Right now the string needs to be correct for the columns to load. I also have some worries about how this impedes performance. I'm not sure what the performance penalty is for this flexibility, but I will continue to look at this. The advantage of the current system is that it does 2 things at once: column flexibility and localization. I might look at using xml instead of the pipe-symbol/semi-colon separators, but the DNN localization editor does not expect this, so I need to look at consequences first.

My suggestion for you is (this is how I do it): Do it one column at a time on a development machine. Keep the resx file open in a text editor and carefully add your columns making sure you add the semi-colon column separator each time (probably it is easiest to add them to the end of the list first). Then, once you have the new columns, delete the old ones and rearrange if necessary. Again one at a time.

Good luck,

Peter

If a column throws an error try adding a few pipe symbols at the end ... Just a tip