Bad Gateway Error for Modx Rev Wiki

Started some work this morning.. And keep getting a 502 Bad gateway error to the Wiki

Is it me is it broke.. what’s happened

I got the same error on two different networks (one is wireless, other cable). So it’s not you.

All I wanted to do is apply the placeholder for content to my template, and add another two placeholders, but now I can’t get to any sort of documentation anywhere.

Admin should put up a mirror of the documentation somewhere else for safe keeping because I am getting the 502 error no matter where I go on the wiki, and I don’t know that the documentation even exists anywhere else. And apparently the wiki has been down quite a bit recently. That’s just not good.

Even If I had an older static copy...

-Doug

I forgot I bought the book.

Another good source of documentation is the wayfinder PDF book.

-Doug

The wiki is back up. There are lingering issues with memory management and Java that crash the SSO app we’re using, Crowd, which in turn causes issues with Confluence.<sarcasm>Java is SO fun.</sarcasm>

Could someone give the wiki a kick please - it’s hard enough not knowing wtf is going on without the documentation dying on you. It’s like the docs know... I’m failing a test.

fx:eeyore Anyhoo. Please could you turnitoffandonagain or whatever you do to clear the bad gateway message. Thx.

I’m getting that at Jira too (happened just now). Hopefully, things will get ironed out soon.

It makes me angry when I think of how much I paid for MODx . . . oh wait . . . never mind.

Well Bob, not all of us have written 4 billion pages of documentation for the blessed system and worked with it for years.

I’m just trying to understand why @RESOURCE resource_id, or @CHUNK chunkname in a TV Input Options box doesn’t do what I’m expecting it to do, and it’s such a little thing, and must be done so often, but I can’t for the life of me get it to work (at all, let alone how I want it to). And it’s hurting my head.

If it’s anything at all like Evo’s @-bindings, @RESOURCE simply returns the content of the specified resource, and @CHUNK does the same for chunks. No processing, just the raw content. You don’t use them in the input options field, but in the default value field.

Thanks Susan (at least your site helped me make more sense of Evo), but from the documentation:

"Please note that @ bindings will work only when used inside "Input Option Values" or "Default Value" fields.

When placing @ bindings inside the "Input Option Values" field, they are used to format input options only when editing document within the Manager, for example to create a drop-down list of Cities or Countries.

When placing @ bindings inside the "Default Value" field the returned value is used to render to the final web page. This makes it simple to build complex forms for data input on the web very quickly. "

I don’t really understand what ’used to format input options only when editing document within the Manager’ means.

And as per usual, I don’t really understand if I’m going about what I want to do all wrong (let a user select a resource to display in a sidebar, from a list of resources (I don’t know how many there will be, so I don’t want to create chunks for the different options s/he might choose - not that this appears to work anyway).

It means I’m wrong.

Input Option Values is what will be used for the resource editing page, and applies to select, radio and checkbox options, when you edit the TV for a given resource. So I suppose @CHUNK would load the content of a given chunk, which should be the list of option values separated by || for the TV to use as name-value pairs for select, radio and check box options.

Default value is what will be used for the final page output; what the visitor will see on the finished page (well, it’s the raw, unformatted value; it will most likely go through another step of formatting, like an image path will have <img ... /> tags added to it, or a date like created_on will be converted to human-readable date-time).