Shawn M

Thanks again for your help! I'm going to wait until a future release before implementing changes (for reasons you've stated---I likely don't have all of the other code from prior fixes).

Thanks again! I followed along with your changes (more for the learning exercise), which successfully removed the 'confirmation_status' boolean from view. However, when a confirmed entry is edited, the radio button automatically changes to 'tentative' now. This could just be on my end, but I wanted to point that out just in case. As a side note: The other boolean fields (start_date, end_date, areas, and rooms) remained after adding the changes. As a quick and dirty fix just to hide these from our...

Thanks again! I followed along with your changes (more for the learning exercise), which successfully removed the 'confirmation_status' boolean from view. However, when a confirmed entry is edited, it automatically changes to 'tentative' now. Could just be on my end, but I wanted to point that out just in case. As a side note: The other boolean fields (start_date, end_date, areas, and rooms) remained after adding the changes. As a quick and dirty fix just to hide these from our end users, I added...

I figured out the CSS portion of my post---the culprit was how text was wrapping/breaking, not any of the table width settings. The code in my custom.css file is now: .dwm_main a { display: block; min-height: inherit; word-break: normal; -webkit-hyphens: none; -moz-hyphens: none; hyphens: none; } Thank you for your help and pointers along the way, I appreciate it!

I tried both of those changes, but they helped some columns and made others worse. I looked at a particularly busy day in the 1.4.11 installation and noticed the table expands horizontally when needed (and adds a scroll bar). Are the tables in 1.7 fixed, or would they do the same? I'll try to test a few other things (looking at 1.4 CSS for clues).

Thanks, Campbell. That line for functions_view.inc did the trick. Setting the CSS Word-Break to 'Normal' also helps a lot. However, longer words are still hyponated and wrapped, or, when there's just 1 or 2 extra characters, clipped (similar to 'Overflow: hidden'). I think it's from differences in how column widths are set in the table. Something is causing room columns with no bookings to maintain an equal share of the overall width (where they used to shrink a little whenever a neighboring column...

Hide fields in view_entry and force word wrap in Day view?

Thanks for the reply. In edit_users, how would I specify which db.usertable to use? I see several references to $tbl_users, but I was unable to locate where that is declared. I could replace $tbl_users with a specified dbname.tablename (like "mrbs.mrbs_users") in edit_users, but I suspect this might create issues elsewhere. In my current db_ext setup, I still get asked to log in twice when switching between installations. It's not a big issue, but one auth session for both apps would be ideal. Would...