alchemycms / alchemy_cms Goto Github PK

If you have a element with a missing content in it a button to add the content shows up.

Pressing the button gives following error inside the javascript console:

500 Internal Server Error - http://localhost:3000/admin/contents?content[element_id]=68&content[name]=twitter&was_missing=true

After reloading the page the content is there.

rake db:seed fails with:

== Created language Deutsch
rake aborted!
uninitialized constant Rails::Logger

under Ruby 1.8.7, Rails 3.0.9

+++++++++ Error: You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.+ +++++++++++++

/Users/tvd/.rvm/gems/ruby-1.8.7-p334/gems/sortifiable-0.2.4/lib/sortifiable.rb:302:in `move_to_bottom'

The Sitemap (Admin::Page.index) is very slow.

Rendering a nested set via Rails partials seems to be very slow.

Maybe we could cache some parts or reduce the number of partials. That is not very DRY, but a lot faster ;)

Since now switching the language means to goto the the root page of the other language.

We should implement a way to stay on the same page and just switch the language. But because languages are just branches in our page tree. So not every page has a corresponding page inside the other language branch. We could store sister pages or something like that.

And get rid of all Rails prototype helpers inside rjs files and controllers and replace them with jQuery and or Alchemy JS Functions

Maybe paperclip

Found a conversion/migration workflow:

https://gist.github.com/375203

Since now we render the first public child as home page.
But maybe some customers want to set the landing page to a different page.

So we should add a landing_page flag to Page and render this page in Pages#index

All admin controllers should be SSL protectable.

We could set a flag for the page_layout defined in the page_layouts.yml wich tells the associated Page that it is not deletable.

Admin-Users should be able to delete this Page with this page_layout, but all other users may not.

Admins should be able to set page editing permissions for each user in the gui backend.

Another thought:

Possibility to grant or deny creation of certain page_layouts.

Question:

Should this automatically include subpages? This would reduce admin workload.

For Browserbased Installation lets implement a installation controller, that migrates the database. Asks for Admin password and User and seeds the database.

The Sprite file icons.png has to be altered. The icons should have more space between them. So resizing them i.e on iPad still looks good.

Maybe we should also align them vertically. So that we could use them easily in front of text.

To speed up performance in the Elements#list window, we should only load Elements from the active cell and load the other elements via remote on activating the tab.

when deleting a picture content from element in admin backend - and picture editor is rendered with option "max_images => 1", you can not add a new Picture-content anymore.

clicking the copy link of an element has no effect.

Failure log in console:
ActionController::RoutingError (No route matches "/admin/clipboard")

And NO, we don't use sphinx, because of lacking auto index feature and not having a serverless mode

If starting a fresh alchemy installation in browser without having page_layouts.yml, elements.yml, ...

You will get a hint in the console log:
Please run: rails generate alchemy_scaffold

This must be changed to:
Please run: rails generate alchemy:scaffold

If one changes the restricted state of a page, then only the page where the change was made changes the icon. The icon of the nested children stays. The value has changed, but the stays the same.

OnClick Event should disable the possibility to add picture from library for a moment.

Since now a page that has a copy in the clipboard can be deleted, because the clipboard just holds the page id.

We should mark pages as deleted instead of destroying them.

After creating an element the element is not draggable and not rendered inside it's correct cell.

While sending Mails (ie: after creating an User) this error accours.

We need to use active model without active record for having validations for the mail model

or make a gem out of it and bring it to rails 3

Since now the user has to delete a page and create a new one if he wants to change the page_layout/type of the page.

The problems with this are the same as altering the page_layouts.yml file:

1. delete elements if not allowed anymore?
2. generate elements that have to be on that page?

Cut an Element and it will be available in clipboard and trashbin.

Taking it from the trashbin and putting it back on any page will cause an error where this Element will neither be assign a position nor a page-id. Although the Element is visible in the Element-Window, reloading will result in loss of that Element.

Back in the good old days there was a washapp branch where we had taggable pictures and files. This would be nice to implement something like folders for big image archives and file archives.

In order to show some dead-link warning, or for automatically redirecting old links we should store all links the user ever sets inside of the EssenceRichtext, EssencePicture and EssenceText.

max_images option is set to 1 in the element.
Assigning a picture to the empty placeholder content, in this moment you will get the possibility to add a new picture content to the element.

Since now saving occurs when changing the picture order via drag'n'drop.
Instead the Element should be set to 'dirty'.
This can be accomplished by saving all Contents in a hidden_field.

http://alchemy.lighthouseapp.com/projects/73309-alchemy-cms/tickets

Lets introduce a Backup Module:

A Backup is a database dump + Uploads Folder zipped as Package.
Multiple Backups should be listed in a Backup module.

Existing pages should be updated if the page_layouts.yml was altered.

What should we do, if Elements are on the page that are not allowed anymore?

• delete? * hide? * ask the user? * If one add elements to autogenerate. Should they be generated?

If you have a page in edit mode and another page is locked and shown as page tab.
Click the close button to free the locked page.
An Error in the Javascript Console appears:

404 Not Found - http://localhost:3000/admin/pages/15/edit

We have this wonderful Drag'n'Drop Trash. We should refactor the Clipboard to act like the Trash.

Add a filter in the Element window. For finding elements in long lists.

After initial signup (localhost:3000/admin) "Unknown action"-Exception is raised.

"The action 'new_alchemy_user_mail' could not be found for Mailer"

Ruby 1.8.7, Rails 3.0.9

Check if Alchemy depends on mysql, or if it also runs with sqlite and/or postgresql

When uploading a picture via FlashUploader the progressbar will turn red.
In console an error is logged:

ActionView::Template::Error (No route matches {:controller=>"admin/essence_pictures", ...

i often realize that I have to ask for Page-objects in the views instead of working modelstrong.
You always have to be careful that you dont forget to built conditions into your logic in this views like asking if page is not restricted, or page is not public, or page is not visible, page with language_id and so on...

we should define some scopes for a this situations we often run into.

In my page_layout I catch all elements of a Page via will_paginate. So i have a pagination.
Then I render these elements on the view, but I have to set an offset and need to assign it to the render_elements helper.

Now I set this as an option in render_elements (standard = nil) and in the Page-Model#find_selected_elements
This is not a big change but you have the opportunity to use will_paginate with elements, like:

<%- news_page = Page.find_by_page_layout('actuals') -%>
<%- @news_elements = Element.paginate_by_page_id_and_name(news_page, 'news', :per_page => 4, :page => params[:page]) %>
<%- offset = !params[:page].blank? ? ((params[:page].to_i == 1) ? 0 : params[:page].to_i) : nil -%>
<%= render_elements(:from_page => news_page, :only => 'news', :count => 2, :offset => offset) %>
<%= will_paginate(@elements) %>

Our Alchemy Installer script should be an executable provided with the gem

In alchemy backend when editing a page with more than one cell:
When creating new elements for a certain cell, it will be created in a wrong cell.
(I take the assumption that the element is always created in the first cell which is found.)