As usual, you're spot on. There was a plug-in that I'd forgotten about on the site.Should let me sort it out from here.

Cheers,

Jayme

"An error occurred while updating. Try again in a while.”

This error “pops up” as soon as they open one particular editor list view and also when they try to save an article in that editor.  It doesn’t happen with any other area or pages in this way so it's very local.

The error shows up in a lightbox dialog with only an "OK" button as a choice.

They're on a modern Mac so I assume they are using Safari (but Chrome may be possible).

Any ideas?

Jayme

J.

J.

Required fields sounds like a good proof of concept type of step. Or perhaps a universal class="element" or class="element-label" just to set the hooks?

For those who base their "application development" types of businesses on CMSB, this sort of feature can go a long way towards the feel of customization that clients appreciates.

J.

A few years ago I sent Dave a suggested set of ideas on how auto-appended classes are handled in some other systems.

Just spitballing here, but:

• Each element could receive one or more classes automatically.
• Classes normally go from the generic to the specific (similar to the way Bootstrap works in your v3 releases).
• So a text-field element might have a class set of "element element-input element-textfield element-<fieldname>".
• A required checkbox element might receive "element element-input element-checkbox element-<fieldname> element-<fieldname>-<index/orValue> required".
• A label for a WYSIWYG editor might receive "element element-label element-label-wysiwyg element-label-<fieldname>". Similar process for help text, pre/post-fixes and description text.
• This needs refining, but something like this would allow users to style all fields with a given font face or size bump, any required fields with a border colour, add margins or padding to spacers, make checkboxes or radio buttons display in two columns, or make a critical product name field stand out so a user notices it. Might also allow for some extra plug-in mojo to happen.
• Could also extend this to List Views with a similar class set of "listview-cell listview-header listview-header-<fieldname>" or "listview-cell listview-<fieldname>".

This is very rough, but it might give someone some ideas.

Jayme

I was pleasantly surprised to find a name auto-appended in this case.

UPDATE:

In case is helps anyone, I found a solution that works in my specific case. The select field is given a name="required_game[]" attribute, so I was able to add:

select[name~="required_game[]"] {min-height: 40em !important; font-size: 90%;}


to the cmsAdmin/custom.css file.

J.

.htaccess cache expiration is a good option but hard to target a single page (needed in this case). Prevailing wisdom is that there is really not foolproof way to do this with on-page code as browsers behave differently.

The situation we now believe to be happening is that the PayPal IPN return was delayed so the member's account was not credited with the product sale. So, it may be unrelated to the CMS.

Research is ongoing. ;)

J.

J.

This new greyHiddenRecords only works for CMSBuilder v.3+. For those of us still working with some v.2 sites, is there a way to limit the styling to a particular table? I've tried variations on the following with no luck:

// register callbacks
addFilter('listRow_trStyle',      'style_certain_records_listRow_trStyle', null, 3);

// **** KEY LINE FOLLOWS ****
function style_certain_records_listRow_trStyle($trStyle, $tableName = "cms_sc_orders", $record) {
    if (!@$record['hidden']) { // All non-hidden records are scanned for new rules.

        // Not locked, but no other checks - should highlight odd situations.
        if(!@$record['locked'] AND !@$record['paid'] AND @$record['order_id'])         
            { return "color: rgb(200,200,200);".$trStyle;  } 
            // pale grey, Order_ID added only to limit styling to Orders table.

    } // end rules for non-hidden fields

  return "color: #CCC;"; // default hidden style
}



and...

function style_certain_records_listRow_trStyle($trStyle, "cms_sc_orders", $record) {
    if (!@$record['hidden']) { // All non-hidden records are scanned for new rules.
// ... styling rules here...
}   
return "color: #CCC;"; // default hidden style
}


In both these cases we're trying to limit these styling rules to affect only the _sc_orders table.

Any ideas?

Jayme

J.

Unexpected output was sent by a program library or plugin.
Output was "

" (4 chars)
Developers: Check plugins and library files for accidentally added whitespace or other characters.

The character count varies The sites that are now throwing this do have additional plug-ins in place but the exact ones vary a bit. Before I run though a range of experiments, I thought I'd ask the experts about this.

Any idea what I should be looking for that might cause this?

Many thanks,

Jayme

Jayme

Thank you.

J.

Has there been any further development on a way to show updatedByUserNum.fullname or updatedByUserNum.username in an editor List View? This has come up again for me with a couple of project and I've not been able to make it work.

Any ideas on how to accomplish this?

Thanks,

Jayme

It would actually be helpful for all the form elements to receive class names. If they had both general (class="prefix') and tied to the element (class = "prefix prefix-myFieldName") in the HTML then we could be very specific with styling code. I remember discussing this option with the team a few years ago.

Jayme

Jayme

Just for discussion, I would think that we'd rather have mod_security running than not though. Although you pros at Interactive Tools probably validate and clean your code, other functions on sites might not have received the same care. This library provides some blanket protections again DDOS and malicious form injections which I'd rather have on if possible. Any thoughts?

Jayme

It normally appears when trying to modify an existing editor field with Advanced settings on a production server. So if you're saving the extra field settings in a lightbox, that's when the error usually appears. "Top Level" changes to the editor, don't seem to trigger this error. I'm guessing it has something to do with the file being loaded into the lightbox for editing.

We've found two work-around so far:

1. Change the editor on another server and FTP the schema over.
2. Manully edit the schema on the production serve and then revisit the Section Editors after doing so.

QUESTION:

Is there a clear directive we can ask our hosts for that would solve this issue? It's affecting a larger number of our sites these days and I don't want to have issue a trouble ticket for each domain if I can help it.

Many thanks,

Jayme

Any idea what steps your host took to resolve this issue?

Cheers,

Jayme

The image library item is just something that's been on the forum wish-list for years and I saw the opportunity to mention.

Mostly, I would hope to include responsive support, avoiding Flash and as minimal an interface as possible by default.

Just my $0.02, Dave.

J.

Wanted:

- DropBox image access support

- Image caption tool

- Local image library (long discussed on these forums)

- Improved MS Word linting on paste functions

- Support for local (per-site) feature inclusion & exclusion - similar to what is currently supported by TinyMCE 3x in CMSBuilder

(Really) Not Wanted:

- Table insert / editing /etc. Hiding all table functions would be my default position

Cheers,

J.