Hi Quick Base Community, If you've seen our March Release Notes, you may have noted this item: To improve the customer experience, we will be retiring our old home pagesÑhome pages created prior to...
Published 7 years ago
Version 1.0
Blog Post
As a developer, I am super amped to change all the old dashboards to the new ones. However, in the process of switching them over I came across a...issue. The mac daddy of all dashboards, that runs all of our tracking, does not work in the new dashboard. It is a dashboard that literally only has one widget, a text editor, that hass HTML/javascript thrown onto it. When I put the code in the new dashboard text editor, I got...code. It no longer recognizes HTML vernacular. So I put it in a rich text page, and then threw the url into a link widged on the new Dashboard. But now the Quickbase native CSS classes no longer work (Vibrant, Success, Alert, etc.), because it is a rich text page within a Quickbase coded page. Everything is being overridden. So now I am going to have to create a new CSS page, which connects to the rich text page, to link onto the new dashboard. A very convoluted solution to something that worked perfectly well before.
Of course, this is a very small issue, luckily with a solution, but it is annoying as all heck, and I hope I don't have to play with this again in a few months when QB comes out with some fancy new UI changes.
Of course, this is a very small issue, luckily with a solution, but it is annoying as all heck, and I hope I don't have to play with this again in a few months when QB comes out with some fancy new UI changes.