the quick search always searches content section regardless of where you are in the cms; should be context aware.

when hitting the file section no folder is selected by default; very confusing for users .. need to have 'your folder' selected at the start

if mtime of two files match then only one is inserted; some code required to handle this

Intermittent on wwt cms (and probably any others that use langauges) a status 6 article will change into a status 1. can't see exactly why, and it doesn't happen often.

The system it's happening on is an IE7 browser.
Check the autosave perhaps?

Can't delete files in files section of CMS (FootyMums) not sure if this issue is CMS wide.

[edit] sorry you cant delete from search results.

the preview button has to autosave, but by default autosave's don't show a loading popup. the preview version of autosave should.

throws a JS error on submit

The current the filesystem on sync and insert commands does not escape values going in, so it is possible to create a file on the server whose name includes sql commands and they would be executed..

Discovered on mensgroom:

INSERT INTO wildfire_file (id,filename,path,rpath,type,size,status,flags) VALUES (1248092082,'ACclassicfragraceperfumed'homme.jpg','/home/mensgroom/public/files/Content-Images','files/Content-Images','image/jpeg','1112','found', 'normal')

Note the ' in the file name which closes off the value string..

When adding permissions to users or copying permissions from other users the records are added on top of existing ones rather than replacing if already set.

Remove the made files from the repo, create these via cap deploy.

this bug is for sheldon, as a reminder to myself, no need to take care of it anyone else :)

the ajax autosave call that triggers on preview clicks is asynchronos, meaning the actual url target of the click has to be cancelled, and a js new page load needs to be fired. This triggers popup blockers in browsers.

This can be done with a synchronos ajax call instead, so it will wait for the callback and carry on after with the target of the a tag, meaning no popup blocker troubles.

1. Remove the padding from below the 3rd level nav
   
2. Add icons
   
3. Sort the spacing between the file browser and upload/info box

Gareth reports styling issue with file boxes...

see http://github.com/phpwax/wildfire/issues/closed#issue/19 for original post

Gareth requests icons as in the visual..

see http://github.com/phpwax/wildfire/issues/closed#issue/19 for original post

need more resources; in depth doc on each section, some videos would be good.

Doesn't have any icons. Please insert.

turn off cache on preview pages, so that people won't be seeing an old version of the page when loading it in their browser. not sure if IE will behave this anyway :(

WWT CMS.

After adding an inline image, you can not scale it to a different size.

a few ways we could do this. but after seeing that youtube have an api for doing uploads I'm tempted there. depends how much they expose, we'll see. if we have to code the transcoder anyway, then S3 would be better.

as its not used most of the time, make it a new plugin that depends on the this one...

At the moment the flash uploader is either flash 10 or 9. would be nice to support 8 through 10 and dynamically switch them based on what the client has.

Add 2 fields to cms_content, a foreign key to the user editing the content and a time the lock was applied. Expire locks after 5 mins in case someone closes their browser. reset lock time on autosaves. if content is locked, disable autosave for subsequent users, and put up a message about saving overwriting remote edits.

wildfire should work from the folder name wildfire, not just cms.

On long listings in the file section the fixed footer sometimes blocks the file details

the comments editing form still uses the previous layout, making it look out of place compared to others.

As the cms keels over and dies in ie6 what should be done about this?

• upgrade box?
• googles chrome frame (risky as its an untested beta)?

Is this really needed? no one seems to use it and it causes whole bunch of styling issues as its absolute & high z-index

Currently all of the js that handles things like filters, categories & images are id based. For example, you can't have more than one image selector in the same page without having serious issues & having to rewrite most of the js anyway.

All of these should be easily portable to any part of the cms; use custom attributes, .closest() etc and run off classes only.

An old issue, but one that doesnt seem to be in the list. With horizontal navigation the length of the menu is determined by the browser window size.. this is a real issue when you 10 modules in the cms .. it makes it a nightmare to use

I'm not what has changed but recently I've noticed that the 'type' field on wildfire_file now contains the character set as well as the mime type... this could a major pain for anyone doing == checks .. like i was on dealer websites...

Why do we store the full path as well as the relative one?

As we know the root (PUBLIC_DIR) surely we dont need this.. and when you move files from one place to another (like renaming a user) they are instantly wrong and a real pain to update

this entire class is a bug in waiting ... hacky to the nth degree ..

the format used by the cms & regex used in the cmstextfilter class for handling local videos do not match; so local videos dont get parsed out properly

this is full of really old stuff ... time to bin off a bunch of it (which probably doesnt work anyway) or at least fix it

references all over the place to things like WXInflections which should be just Inflections. Need sorting before the old ones are dropped

Tidy up the code base by removing old functions that are from old versions of the cms

why is this very custom action sitting in the cms_content model?

Are we going to remove this? These days we mostly extend classes for new values rather than using that ..

it doesnt support validation, front end code to use it is ugly at best, duplication occurs and adds large overhead to saving of cms_content

power though extension as oop ppl would say ..

The model has this field but no where on the cms makes use of it or give ability to edit it ... is this old and forgot or new and unimplemented?

several cms classes (like cms user) are old and still hanging around, extending other old classes .. are we going to dump these?

wow, thats an ugly looking class .. can we refactor to something nicer

Can we change all the classes that are in current use to use the same prefix ... so its clear to an new dev which are old and which are new ... im not fussed if we use wildfire or cms .. but consistency is good.

We dont use these any more ... lets drop them and clean up the code base

can we make this consistent on all controllers ..

more than one in the repo .. one marked as f9 .. other not not marked .. can we keep a naming convention on these and mark both .. should make it easier for the flash to then be swapped ... see
http://github.com/phpwax/wildfire/issues#issue/33

remove all js/css/image files that arent being used to tidy the code base

why is there a date picker call when we dont use one?

should replace with a ajax call to sort entire list (http://github.com/phpwax/wildfire/issues#issue/29) then can remove this function call

do we really need this? whats wrong with a label?

The filesystem js needs a serious tidy before can even thing about sorting the scoping issues

if using vars you want globally scoped declare them at the top of your js file with a nice comment about what they are for & where they are used. Avoid creating vars without the var keyword.

Done many times for vars that hold timeouts etc

actions that do similar things should be standardised and reduced to a common function.

for example the difference between adding an image & a category is minimal. why not make one function that ran from the class, used the attributes (custom ones if needed - cms doesnt validate to xhtml anyway) and posted to where the href says (maybe adding a suffix so the code can not show the layout)

This will reduce errors, simplify the js and make changing routines much easier ...

better if js functions are dumb & just use what they are told instead of trying to work things out themselves.

As it stands atm if a js error triggers page titles cant be edited .. considering the size and complexity of the js; this is surely a bad idea; title is a fundamental part of the a page

do we really need 30+ lines of js just so people can change a title of a page and have a pencil icon & yellow colour?

are moving over to new waxforms in the cms?

is there a particular reason we need both?

risky to use id as a param ... as the request model mixes in the url mapping .. for safety should be changed to something not in the url mapping .. like 'uid'?

I though site helpers where loaded in anyway? does it need the include_from_registry call?

non modal previews trigger popup blocking in firefox (probably the other browsers too). need to modify this to "just work". it's got to do with cause event in js, have a branch with work for this called preview_popup_block. doesn't quite work yet, but the idea is a synchronous ajax save, and then a fire the new window, instead of firing it on a callback.

should be replaced with Request calls

add a check to see if there is a reason to trigger

Causes updating problems as regularly forget about the file.html .. cant think of a could reason to keep it.. make it one only

Cropping is ropey .. the selected area remains there after crop has happened...

Due to the nbsp inserted at the front you can not navigate though a drop down by letters ... how about right align the text and add spaces to the right hand side .. so start with 10 for top level and reduce for each child

needs a good tidying

parse_xml - doesnt seem to be uses any more .. remove

only seems to be referenced in the controllers... remove unless can see where its used..

generally we use $model for the model being edited but on some we also use $this->page .. lets just one for simplicity

example - the add_image functions

currently messy, lots of bugs been reported from wwt and they still say they have issues ... needs a serious testing (by n00bs & nerds) ..

seems redundant .. function is empty .. cant see any references to it either .. remove

not in use... replaced by permissions system .. needs removing

this should really be moved out of the CMSApplicationController into the relevant controller and re written

Used a lot within the controllers, should be replaced with Request where possible

On the wysiwyg have several insert x buttons .. each one uses a dialog that looks and behaves differently .. not good for users .. amalgamate as much as possible

section filter not maintained.. not a big issue on small site .. but on something like wwt who have dozens of sections and hundreds of pages can be bit of a pain to keep having to find the section you filtered by

like content comments have multiple statuses .. why not show them in the same why.
- green = live - red=hidden - orange=spam

rather than hiding it in another section, its inconsistent.

any partial that is just a render of another partial can be changed at the source to render a different partial. if it's an explicit partial render then just point to the other one or if it's a controller action just use use_view to change it.

in order to maintain tree these are recursively read in, but the order is file mod / create time .. not very helpful for a user..

good example, if i have 5 folder, each 3 subfolders and then those have a 100 each the list is huge and without alphabetical order its a nightmare to find things..

couple this with http://github.com/phpwax/wildfire/issues#issue/94 then that drop down might as well not be there for the use it is..

styling on the tabs break horribly if they dont have one of the id's .. things like this should be classes based

I know the tab is useful for sticking extra content in put I'd rather the published & expire date werent in there .. Far to easy to forgot to fill them in; on sites that dont update regularly (like abstract, eic etc) means the story only has a life of one year .. which is on the short side when the sites only change content once every 6 months..

move them to main tab with status & section

reference to http://github.com/phpwax/wildfire/issues/#issue/110

don't unpublish content after a time at all by default. ever. this is really bad.

the inline category creation in the content editing form (it's on the category tab) should clear the text after creation.

when I insert a local video, then after that insert a remote one, the local one goes in instead.

apparently you dont need a name for a category..

as there is no required fields, simply click on the create button and get a new category ..

after using a filter to try and find something without avail the returned message is very generic & incorrect.

"No categories setup yet"

I have categories, I just couldnt find any.

On a list page, if i have pagination and use the filter the pagination does not change .. needs to be hidden as its misleading to say i have 10 pages when i can only see 1 item.

with the js using hardcoded relative paths (like ../../add_image/) adding or removing a trailing slash from the url of an edit page effects the destination of ajax calls...

dont use relative paths, find you target for the ajax call from somewhere else

anything under 1129px wide create horizontal bar

If i have a draft item with a publish date set clicking publish live wipes the selected publish date and replaces it with current date.

This makes turning off old content and editing a pain as have to go back in again to reset the publish date to what i wanted

so you have pages with no titles .. and that will probably give them a blank url field ... ouch

there arent any ... can easily make sections with out titles; and therefor bad urls

why is the save for later button red? red implies a negative .. like delete .. how about something neutral?

only shows published items .. surely the most recent things people are working on are those that arent live yet.

code is still floating around in the controllers... needs removing

Doesn't seem to be used any more, layout loops over menu_modules instead.

should do only what it says on the tin .. save .. let other areas handle redirects

when publishing without a master the edit function does not call the after save hook

when publishing the before save hook is never called

swap these over to the new partial system

in order to do the joining of items on content we create a dummy item ... to keep consistency shall we do this for all of them? so create forwards to an edit.

the buttons "save for later" or "publish live" were much bigger than they are now. they were reduced very badly and have jaggy edging

Initial bog of form submit has been fixed, hitting submit now triggers the statistics graph to be reloaded instead

http://github.com/phpwax/wildfire/issues/closed#issue/51

has been closed, cant see how to reopen it .. v3 this still happens

http://github.com/phpwax/wildfire/issues/closed/#issue/50

they really need to add a re open feature

http://github.com/phpwax/wildfire/issues/closed/#issue/44

needs fixing in v3

if 2 different async ajax calls happen at the same time, e.g. auto saving triggers while you're busy loading images via a filter, then the loading dialog dissappears and the 1st ajax action continues without visual indication.

possible fix: have a stack that gets added to when ajax actions happen, and then poped off when they finish. only take away the loading screen when there's nothing on the stack.

edit a title, tab off, highlight stays there.

non alpha-numeric characters trigger the filters ... found this while tabbing around

if you tab off rather than click result list stays visible until click on something

http://github.com/phpwax/wildfire/issues/closed/#issue/47