infinitas / infinitas Goto Github PK

Where should be cakephp folder?
In app/CakeHp?

Notice (8): Trying to get property of non-object [APP/Core/Libs/Controller/Component/InfinitasComponent.php, line 235]

Fatal error: Call to a member function trigger() on a non-object in /var/www/user44819/data/www/site/Core/Libs/Controller/Component/InfinitasComponent.php on line 235

To use slugged URL's in the current version its required to use callbacks that figure out the best url based on the params available. This requires some messy code with lots of switch / if/else statements.

Forward routing (from data -> URL)

This should all be replaced with some more low level routing that will allow applications to simply link with the plugin/controller/action/id. The router will then make a callback to a method that will do a find on the model to get the required params.

Reverse routing (from URL -> data)

The router will break down the URL as per normal, and then do a find on the model to fetch the id if its not present. The id is then added to the request so that the controller action will always be given the id and there is no need to figure it out based on various params such as slugs and so on.

All the current code for URLs will need replacing (only frontend uses onSlugUrl event). All plugins will require some basic code for figuring out the data which could probably be abstracted, so only some plugins will need special code to handle this.

similar to the facebook like and twitter button

http://www.google.com/webmasters/+1/button/index.html

<!-- Place this tag in your head or just before your close body tag -->
<script type="text/javascript" src="http://apis.google.com/js/plusone.js"></script>

<!-- Place this tag where you want the +1 button to render -->
<g:plusone href="<?php echo Router::url($this->here, true); ?>"></g:plusone>

Something similar to:

rating += (count email addresses by ip) - 1

This will add 0 for people that posted using one email from one ip

adds to people posting from a single ip as multiple people. (could affect companies)

Hi, I did not worked on bootstrap. I am willing to use this cms but when run in browser after installing it, I get error

"could not load /assets/less/bootstrep/reset.less(404)" in front.less.
Please help me how can I do this.

After the modules have been moved around some of the db sample data still uses the old location causing element not found errors.

This is breaking some things on new installs such as relations in various places.

Create many sites from a single install. Require new table for sites and fk in most tables to filter by

would be good to have a shell that is something like htop for the system. this could show some things like crons as they are running. load, visitors etc

http://www.franzone.com/2007/09/17/monitor-processes-with-bash-scripts/ is a good start

This error happens when I install cms:
SQLSTATE[42S01]
le or view already exists: 1050 Table 'inf_acos' already exists
Help me please!

this code should be refactored into a spam filter lib that can be used all over (eg: email contact forms) the comment model can just check in beforeSave that it is not spam,

could also be a validation rule

Along side (or in side) the default theme there should be a print theme which has basic styles for printing.

This could even be just a base which devs could import and extend

some shell methods to migrate from other popular systems to infinitas.

The weight is always 0 regardless of how the tag is used. This should be calculated so that the tag clouds will have different sized tags.

This should just show the login error instead of breaking

This could probably go on to include modules too, where possible mark-up should be done with mustache and stored in the db for easy editing by users.

Currently major views such as index / view for the front-end of plugins is done with the Layouts in the contents plugin.

This is part of #59

Notice (1024): Element Not Found: Blog.Elements/modules/post_tag_cloud/module.ctp [APP/CakePHP/lib/Cake/View/View.php, line 421]

Notice (1024): Element Not Found: Blog.Elements/modules/popular_posts/module.ctp [APP/CakePHP/lib/Cake/View/View.php, line 421]

Notice (1024): Element Not Found: Blog.Elements/modules/latest_posts/module.ctp [APP/CakePHP/lib/Cake/View/View.php, line 421]

These need to be updated in the core install data so that they work out the box after installing.

Its been a while, could update Font Awesome too

this is needed for a number of things (such as #64), posts and forms can be disabled, along with things like stopping view counters being incremented by disabling viewable.

Due to this it does not reload

Part of #59

Error: Could not load module "Blog.modules/snip/module"

Reported by Jelle Henkens | August 1st, 2011 @ 12:23 PM

By loading the pluginName cache in events.php before everything else and remove the array key check in the function _extractPluginName() you will get a performance increase of about 40 - 50 ms if you have about 3500 event calls.

when something is activated/deactivated it should filter, ie

1
   1.1
      1.1.1

if 1.1.1 is activated 1 and 1.1 should be activated.

when 1.1 is deactivated 1.1.1 should also be deactivated.

Although the finds will work fine and only pull records it should, this will just cause less confusion for admins.. when 1.1 is deactivated and 1.1.1 is active things in 1.1.1 should not be in the find, but they will see it is active and wonder why its "not working"

ordering lots of things up and down takes ages. need a input box with the position so you can enter new positions for a whole lot of rows and then just save all at once.

detecting if a visitor is a bot and then not running things like HtmlHelper and Javascript things will save a little and help with page rendering speed.

Currently Infinitas needs to be installed in the top level and not in a sub folder. This is because all assets are hard coded with /full/paths/to/asset.ext instead of being relative to where its loaded from with something like ../../../foo.bar.

This affects all current asset code (images, css, js etc)

When entering the passwords on the shell installer it should behave similar to other *nix password prompts (eg: not echo back the input)

Hi, I like your cms. And think its best of cms's based on cakephp.
Your site is good.
My question - does it (cms) work?
Thank you!

There needs to be some kind of workflow within the admin for new content which would work for all types of content.

Eg: set the site up so that some type of user can create content but another type of user needs to activate it.

This would help with situations where the store owner would like to check each new product has the correct price / options before it goes live.

This gets stuck in a loop after all details have been entered. needs adding the admin user and writing the database file to config