Opal
Activity
From 02/24/2010 to 03/25/2010
03/25/2010
-
09:37 PM Feature #120: Make Advanced Search Better
- I've fixed the OR lookup problem by creating a hash of Item IDs found that match each feature selected. I then took that hash and selected only the common Item IDs that had a match for EVERY feature, using this function: ...
-
- Ahh! The new injection-proof code listed above for the New Feature search will only work with a OR-type lookup in mysql. This means that all items with one matching feature(out of all selected) will be listed. This is not what we want!
03/23/2010
-
- There's not much to separate in terms of CSS, so we'll leave CSS as it is for this version. This is a good place to finish for this request.
03/21/2010
-
- The Pages section of the Admin Area has been revamped. There's better organization and separation for viewing public/system pages, and You can now use the new "TinyMCE Wysiwysg HTML Editor":http://dev.hulihanapplications.com/issues/show/129 on any...
-
-
- Everything Looks good. TinyMCE and Sanitize are playing together nicely.
-
- Next Up: Add custom Image selection to TinyMCE so users can select images to post on Pages and Item Descriptions. * Update: I'm going to hold off on this one for a later release.
03/20/2010
-
- Done Tuning Sanitize to match TinyMCE.
-
- Next Up: Testing *TinyMCE* against *Sanitize*! If Sanitize eliminates a desired feature, we can add the appropriate HTML tag, element, or attribute to the HTML whitelist(config/whitelist_html.yml) so it will not be sanitized.
-
- I Also implemented "Sanitize":http://wonko.com/post/sanitize gem to clean up any malicious code a user might enter into the Wysiwyg editor. All allowed HTML tags are stored in *config/whitelist_html.yml*, so if you want to enable/disable certa...
-
- Added "TinyMCE Plugin":http://github.com/kete/tiny_mce, it is now active for All Pages in the Admin Area. Next Up: Add Wysiwyg Functionality to Item Descriptions.
-
- Packed all core files into public/core. I also seperated all core js from theme js in each theme's application.js file and moved it into public/core/javascripts/application.js. Next Up: Seperate Core CSS from Theme CSS.
-
- Right now, Each theme directory contains everything(icons, javascript libraries, stylesheets, etc.) used in the theme's interface in Opal. Since some stuff is redundant(like jquery libraries, etc.), we should seperate The Opal Core components from...
03/16/2010
-
- We need a "Forgot Username/Forgot Password" feature.
03/13/2010
-
- Looking Good, just a little more testing before I can sign off on this...
-
- Just to clarify, I mentioned that Opal's advanced search now performs *sql sanitation for an unlimited number of different conditions* for _FeatureValues_. Since we don't know how many Features a user is going to search for, we need to make the sa...
-
- We've beefed up Opal's Advanced search quite a bit! * First, we've implemented the new Feature "Search Types":http://dev.hulihanapplications.com/issues/show/137, which allows for the searching user to search for feature values in different ways...
-
- We've added a new cool attribute to the Feature Plugin: Search Types! When an admin is creating a feature, they can specify how This feature can be searched in Opal's *Advanced Search*. So far, there's a couple of different options you can specify...
-
-
- Done! I've added the feature value options a user can select as a simple HTML select drop-down box for now.
03/12/2010
-
- Admin View & Controller Code done! Next Up: Item Plugin Controller & View code.
-
- Created the PluginFeatureValueOption(long, I know) model and db structure. Up next: Controller & View code for Features Area in Admin Section.
-
-
- Every Opal theme can now have its own custom favicon! To add a custom favicon to a particular theme, just upload the favicon.ico file to the images subdirectory in the theme's directory, For example: * opal/public/themes/white_square/images/fav...
-
- Right now, users can only enter in text-based values for features. Is there a way we can create Feature Value Options that a user can select from? For example, If you're listing shirts and you want to specify a Size value, instead of Typing in "Me...
-
- I've spruced up the Features section in the *Plugins Section* of the Admin area. Admins can also now edit Item Features, too!
-
- Done! Admins can now edit Main Feature Attributes.
-
- Right now, admins can only create and delete Item Features(Plugin: Feature). Can we change this?
03/11/2010
-
- I've updated the user messaging system. I've also added better navigation for viewing read/unread/sent messages. Also, Admins can now view every message in the system, as well as any message for a particular user. Admins can access these new featu...
03/10/2010
-
-
- Old and Dead...
-
03/09/2010
-
- Done!
-
- Right now, Item Files(for the Plugin: Files) are stored in public/item_files. We should move this out of the public folder, so people can't directly access files.
03/08/2010
-
- Everything testing well. All Done!
-
- Looks good!
-
- We should add a wysiwyg editor for different things in opal(like pages, Item Descriptions, and more). For security problems, use "Sanitize":http://wonko.com/post/sanitize to scrub new html for bad tags like <form, <script, etc.
03/06/2010
-
- Just about done with all the coding. I also added a "Requires Your Approval" Attention box to the the User Home Page and the My Items page for users. This will show them any new plugin items that need to be approved. Next Up: Testing!
-
- I added a *Latest Logins* Box to the Users Area in the Admin Section. This will show Admins the last 5 users that have logged in.
-
- I also added a "Requires Your Approval" Attention box to the the User Home Page and the My Items page for users. This will show them any new plugin items that need to be approved. Testing Almost done...
03/05/2010
-
- Now that user groups are being implemented, Each plugin has special group permissions called GroupPluginPermissions. These let you specify which groups of people can add/add with owner approval/update/delete plugins for items. These permissions ca...
-
- Finished Approval View & Controller code. The first round of Group Permissions is almost done! Next up: Testing...
03/04/2010
03/03/2010
-
- Fixed! Some background behind this problem: The print function for categories is pretty elaborate. For every level it descends in hierarchy(let's say you have a child of a child of a child), the category's name gets indented and the name's length ...
-
- When I create a lot of child categories under one parent(so we're only looking at a depth of 1), each one gets truncated more when I'm browsing my site. Can you fix this?
-
- Finished visibility coding in each Plugin View for Group Plugin Permissions. Next up: Coding for Item Owners to Approve Plugin items created by other users.
-
- Done!
-
- Let users change their Item's main image!
02/27/2010
-
- Completed Group Plugin Permissions code for changing a group's permissions in regards to plugins for any item. This will be the first Group Permission type to be active. Through this particular set of Permissions, you can change what groups can do...
02/26/2010
-
- Created Group Controller & Views. Also added the ability to change a user's group when editing a user.
-
- Let's revamp the user message interface to make it cleaner and easier to use!
-
- I'd like to be able to let other people add Plugin Items to my items. So if someone comes along and wants to add an Image to one of my items, they can upload it, but I have to approve it before it belongs to the item for good. We should do this on...
Also available in: Atom