bigtreecms / bigtree-cms Goto Github PK

Module designer is adding actions as icon_small_home and icon_small_add -- they should be just "add" and "home".
It's also making the positions wrong (view should be before add).

Long URLs in the "Properties" section in Pages are cut off and do not properly truncate with "...".

Looks like the javascript throws a bunch of errors on hidden pages, the page ID isn't being set correctly.

Looks like if you add an image, preview the changes to the page, then come back to continue editing, the resources in the WYSIWYG aren't decoded properly. The image still has the {www_root} flag in it.

Line 64 of developer/modules/views/create -- double decodes the $options variable.

After adding a folder, the modal blocker stays visible.

... this is bad.

When viewing a grouped module, the 2nd breadcrumb links back to the modules landing page, not the group page.

If the nav item is visible and edited by an admin, it becomes hidden.

When creating a custom field type, selecting "Callouts" under user case doesn't save. You have to re-edit and click "Callotus" again.

We're installing the Home and Content templates by default. Really, the home template is never (or rarely) used for anything but the home page. Maybe we hide it from the chooseable templates (or at least make Content the default for new pages).

When editing a database pop list, it doesn't remember the "Description Field" sort order in the options modal.

When linking up something using the File Manager with local storage enabled, it returns the {wwwroot} link instead of the human readable one. Probably is fine on save, but it looks bad.

Pasting into a TinyMCE window gives an error about json_encoder.

Fix notices in installer and admin router.

If a parent has too many children when you try to reorder the children it fails with the following error : "NetworkError: 414 Request-URI Too Large". I believe this limitation could be avoided if we didn't post every pages order, but instead posted the changed page and it's new location and then calculated the effect on the remaining children.

They aren't using the thumbnail, instead loading the full image.

They don't have +s.

Exif_read_data can throw warnings on corrupt images. It should be silenced.

Remove the option from the pop-up.

After a fresh install, the home page's content age is "735007 Days," which isn't exactly accurate.

The file browser pop below the callout modal when browsing for a photo. The "Browse" button is also too wide and breaks to a new line, shrinking padding seems to fix it.

Sometimes when you use letter keys to switch types in a dropdown clicking "Options" for the field type will pull up the wrong one.

The "Sorry" page for trying to create a view without the appropriate columns is really ugly.

Also, it shows up when you try to create an Image View even if you didn't set it to enable being draggable.

Fields already get hard IDs, I don't think wrappers are all that useful.

The headers for custom view actions show the route instead of the title.

After adding a bunch of pending entries, I reordered them. After adding another item, the view showed empty lines. I then went and published all the changes. The view now has all the approved item, but is also listing the blank entries. View caching problem?

The default template resource names aren't written to the template files that are created in BigTreeAdmin::createTemplate

When using an upload directory (for an "upload" field type) do an rtrim() on the directory and add the trailing / in case they forgot.

Hide the generated route as an option in the template creator.

if an image upload field has an existing image, then you remove that image, then click browse and select a photo from the browser it never repopulates and does not save. Leaving the existing image and browsing works, as does browsing from an empty field.

Looks like home can only have a basic template. Maybe we change it so it can use a routed template or disable the routed templates in the selection screen.

It would be cool to be able to build out a routed template from home, more web-appy, removing that extra piece of the URL string.

Can we hide the "views" column until they have set up analytics? Seems silly to show all 0's.

See: trying to create a second view for a module (icon is missing, broken image in Safari).

Try opening the file browser, clicking into a folder, then uploading an image. But don't actually upload it, just bring up the OS file picker. Now hit cancel or the esc key. The file browser will close entirely, and if you try to open it again, everything goes all crazy.

When hitting "view in bigtree" from the toolbar, you aren't returned to the front (I'm assuming that's what the query string is for?).

Since admins and developers have full access and the permissions table is ignored, we should just hide that section. The text about permissions being ignored can fill the space as a full paragraph. It is very confusing even with the line of text

/pages/move/ defaults to allowing move of the homepage, just like /pages/move/0/. I know we've hidden the tab, but somehow a client managed to move the homepage, so it's showing up in the main nav, as well as being the main nav.

Recursive-Site-Architecture FTW!

When using the Front End Editing feature of BigTree it seems like a lot of the "plugins" don't function properly (i.e. choosing an H2 style, the dropdown doesn't work -- using the code editor doesn't work, etc).

Browsing for an image/file in the front end editor doesn't work, just closes all modals. Maybe we don't allow file uploading/image processing on the front end (like how we hide the callouts)?

The Add Resource button when building templates/sidelets/forms could really use a + icon.

When creating a new template, the array of items field type options do not save. Must edit and re-enter.

I made some changes in a fork of the project to improve the UI when adding unused fields. The select element is now more tightly coupled with the Add button, and have added in some JS hooks to show/hide the functionality depending on whether there are any fields available.

https://github.com/philp/BigTree-CMS/tree/4.0_philp_branch

Should convert {wwwroot} to $www_root when caching view data.

^^ Also, the new adder thing looks strange, don't know why.

The List and Array of Items field types take their key/title pairs in different order, should be consistent.

Can we get these to be respectful of tab indexes of the text area they replace...?

Error state of TinyMCE fields has red left/right border but not top/bottom.

When editing a callout in a page, and multiple types of callouts exists, selecting a different callout type doesn't refresh the form. After doing a bit of searching, it seems that the bind method for loading the new form is failing, and can be fixed by changing:

$("#callout_type select").bind("select:changed",function(event,data) {

to:

$("#callout_type select").bind("changed",function(event,data) {

This is the same for editing and adding callouts.

The different modals need to be consistently positioned, either fixed or absolute, right now it's weird that some scroll while others don't.