Theme and Plugin Roll Call

[Paul Gardner]

Hi everyone,

I've volunteered to try and get to grips on what Croogo themes and plugins are available in the community so I can update the following pages:

• http://wiki.croogo.org/extensions/plugins
  
• http://wiki.croogo.org/extensions/themes

Fahad has just announced a new docs site, so will also add there (http://docs.croogo.org)

If you've got any themes, plugins or anything else you would like to share with the community, reply to this thread with the following details:

• Type: [theme|plugin|etc]
• Name:
• Description:
• Author:
• Croogo Version(s):

HTH, Paul.

[Steven van Oosten]

Type: Theme

Name; BsCroogo

Description: Basic Theme based on Bootstrap with auto show/hide left and right column

Author: Steven van Oosten

Croogo Version: 1.5

Git: https://github.com/stevenvanoosten/BsCroogo

Demo: http://www.santoswebdesign.nl/cm/ (i will chance the adress soon).

More:

It is just a basic theme. But I am proud on it because it is the first theme i build for Croogo (i used to build for Joomla). I like the system and CakePHP is very well documented. 

I will built some more themes soon. I like theming very much because the combination of designing and programming.

Other Question: Croogo cache everything. For developing it is annoying. Do you have a solution for it (disable caching)?

Op woensdag 15 mei 2013 17:21:09 UTC+2 schreef Paul Gardner het volgende:

[Fahad Ibnay Heylaal]

set these to false:

https://github.com/croogo/croogo/blob/master/Controller/AppController.php#L79

https://github.com/croogo/croogo/blob/master/Model/AppModel.php#L26

--
Fahad Ibnay Heylaal
http://fahad19.com

--
--
You received this message because you are subscribed to the Croogo mailing list.
To post to this group, send email to cro...@googlegroups.com
To unsubscribe from this group, send email to
croogo+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/croogo?hl=en
Visit the official website at http://www.croogo.org
 
---
You received this message because you are subscribed to the Google Groups "Croogo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to croogo+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Elias Coronado]

• Type: Plugin
• Name: NodeTypeLister
• Description: Adds a child menu to the List menu inside Nodes to display node types and access the list of filtered elements directly.
• Author: ecoreng
• Croogo Version(s): 1.5

https://github.com/ecoreng/NodeTypeLister/

Im going to fix the other one that i have to list it here too.

Thank you

[Paul Gardner]

I started this thread so had better add some of my own I suppose.  More to follow next week hopefully:

• Type: Plugin
• Name: ElFinder
• Description
• Replaces FileManager/Attachments/admin_index with a more advanced file manager allowing folder management, context menus, drag and drop uploads/moves and image editing amongst other things.  
• Also, if you install this and my TinyMCE 4 plugin it will automatically set TinyMCE's image/file browser to use elFinder.
• Author: phpMagpie
• Croogo Version(s): 1.5

• Type: Plugin
• Name: TinyMCE
• Description
• Integrates TinyMCE 4 (a vast improvement on previous versions) into Croogo 1.5 via the WYSIWYG plugin.
• Also, if you install this and my elFinder plugin it will automatically set TinyMCE's image/file browser to use elFinder.
• Author: phpMagpie
• Croogo Version(s): 1.5

Note: for both plugins you need to create symlinks, details in the readme files.

[Paul Gardner]

I've tidied up the two plugins above and release a MoxieManager plugin, for those willing to pay the license fee to use MoxieManager that is.

• Type: Plugin
• Name: MoxieManager
• Description

• Replaces FileManager/Attachments/admin_index with a more advanced file manager allowing folder management, context menus, drag and drop uploads/moves and image editing amongst other things.  

• Auto integrates with core Ckeditor and my Tinymce plugins for use as a file browser

• Author: phpMagpie
• Croogo Version(s): 1.5

https://github.com/phpMagpie/MoxieManager

https://github.com/phpMagpie/ElFinder

https://github.com/phpMagpie/Tinymce

[Elias Coronado]

Type: Plugin

Name: DebugKit

Description: DebugKit provides a debugging toolbar and enhanced debugging tools for CakePHP applications. This plugin is just a wrapper and just hooks it to Croogo, and lets you activate it. fahad19 did it first, i just updated it to work in Croogo 1.5.2

Author: Mark Story

Croogo v: 1.5

If theres a better version just ignore this then.

[Elias Coronado]

https://github.com/ecoreng/DebugKit

forgot that

updates on this?

[GB]

Paul,

Thanks for serving in this role.  New to CROOGO but been around Cake forawhile.  I have a Bootstrap template that I am trying to adapt to CROOGO and was hoping to get some direction on correct approaches to take.  I'm sure I could brute force the thing but prefer to stick close to conventions of Cake/Croogo.  As Croogo grows, this will probably be a common task, I'm willing to write up what I learn once I'm done.

So some questions:
- I noticed Croogo has 'regions', which Cake adopted recently.  Is Croogo best practice to use Croogo regions?  Cake regions?  Are they the same? 
- My first step was to take a Croogo menu and make it populate the HTML menu for the template I have.  When I inserted the Croogo code to do that, I got the Croogo HTML and CSS and need to adapt this to my template. I will need to do a similar function in several different areas of the template.  What is the correct way to adapt this?  Elements?  Custom Layout?  Adapt template to Croogo?  Other?
- I have other node types that I want to use to populate e.g. sliders, etc.  They all require more information than is available in the node table:  e.g. my slider nodes will have in addition to title, body:   image/video URL, timing.  WordPress uses a metadata function to extend the data required by a node.  What is best way to achieve in Cake?  I tried to navigate the taxonomy stuff without success.  Is extending the fields of 'nodes' taboo?  I'm guessing I could write a Cake MVC to do it but would think this is a common problem run into by CMS users.

Thanks in advance!

George

[Rachman Chavik]

On Fri, 16 Aug 2013 21:11:02 -0700, GB wrote:

> Paul,
>
> Thanks for serving in this role. New to CROOGO but been around Cake
> forawhile. I have a Bootstrap template that I am trying to adapt to CROOGO
> and was hoping to get some direction on correct approaches to take. I'm
> sure I could brute force the thing but prefer to stick close to conventions
> of Cake/Croogo. As Croogo grows, this will probably be a common task, I'm
> willing to write up what I learn once I'm done.
>
> So some questions:
> - I noticed Croogo has 'regions', which Cake adopted recently. Is Croogo
> best practice to use Croogo regions? Cake regions? Are they the same?

I think you're thinking of view blocks. Cake does not have 'region' per se.
They are different.

> - My first step was to take a Croogo menu and make it populate the HTML
> menu for the template I have. When I inserted the Croogo code to do that,
> I got the Croogo HTML and CSS and need to adapt this to my template. I will
> need to do a similar function in several different areas of the template.
> What is the correct way to adapt this? Elements? Custom Layout? Adapt
> template to Croogo? Other?

Themes.

You can override most of Croogo's default template using themes.
https://github.com/rchavik/Readable-Theme has some example for:

- Override Nodes views:
https://github.com/rchavik/Readable-Theme/tree/master/Plugin/Nodes/Nodes

- Override email template from a plugin:
https://github.com/rchavik/Readable-Theme/blob/master/Plugin/Contacts/Emails/text/contact.ctp

- Generate custom markup for menu:
https://github.com/rchavik/Readable-Theme/blob/master/Helper/CustomHelper.php

> - I have other node types that I want to use to populate e.g. sliders,
> etc. They all require more information than is available in the node
> table: e.g. my slider nodes will have in addition to title, body:
> image/video URL, timing. WordPress uses a metadata function to extend the
> data required by a node.

We have something similar: CustomFields. We could use this feature to store
simple key value attributes in the database. The Meta plugin uses this to store
meta_keywords and meta_description for each node.

However, I would recommend _against_ using this for data that will be used
in 'reports'. For example, if you have an 'Book' content type, don't store the
authors using custom fields.

> What is best way to achieve in Cake? I tried to
> navigate the taxonomy stuff without success. Is extending the fields of
> 'nodes' taboo?

Personally, I don't think it's taboo. But you'll have to figure out a way to make
it easy for upgrade. So, try not to modify the Nodes plugin itself. Instead, create
a separate plugin and extend the core Node MVC.

Using the previous 'book' content type, you could create a new Books plugin:
- Nodes.Node hasOne Books.BookDetail (with conditions where 'type' => 'book'). Inject
the relationship using Croogo::hookModelProperty()
- BookDetail model has the author_id, isbn_number, publish_date, etc.
- Use the Migrations plugin to create your book_details table, etc.
- Create the tab elements for /admin displaying custom book detail fields, and display
it using Croogo::hookAdminTab()
- If needed, create Books.BooksNodeController and Books.BooksNode to implement your
specific needs. Or use a behavior.

Extending a plugin is a bit hard to get right, but doable.

[GB]

Very helpful and timely, thanks a bunch!

G

On Wednesday, May 15, 2013 11:21:09 AM UTC-4, Paul Gardner wrote:

[GB]

Very helpful and timely, thanks a bunch!

G