Hey everyone,

I’m somewhat a big fan of Twig and I’ve been using it for quite some time now in my CodeIgniter applications. Therefore I decided to release my implementation of Twig for CI and share it with everyone.

In a nutshell, Twiggy is not just a wrapper for Twig. I added some neat functions to make life easier when dealing with themes, templates and layouts.

Github page: http://edmundask.github.com/codeigniter-twiggy/

I also created a demo (example) application to show how it could be used. I’ll update it by adding more examples and documenting them.

Demo (example) application: https://github.com/edmundask/codeigniter-twiggy-demo

Let me know if you find it useful.

I get the error message when I try to use demo :Fatal error: func_get_args(): Can’t be used as a function parameter in C:\xampp\htdocs\CI-twiggy\sparks\Twiggy\0.8.3\libraries\Twiggy.php on line 154

Try to clone the repository again, it should work now. It probably has something to do with your server setup. If it fixes the problem, I’ll update the main repo (twiggy spark) as well.

I try to clone the repository,I have the same error message :s
Fatal error: func_get_args(): Can’t be used as a function parameter in C:\xampp\htdocs\CI-twiggy\sparks\Twiggy\0.8.4\libraries\Twiggy.php on line 154

I only updated the demo app, not the spark repository: https://github.com/edmundask/codeigniter-twiggy-demo/commit/106de1751b048a7687e8556a9d49746f0dc34933

You’re using Twiggy v0.8.4 while the demo app is using v0.8.3 (for the time being), so I assume you’re doing some testing of your own. You can look at the commit that I’ve posted here and change a few lines of code yourself to get rid of the error. I’ll roll out Twiggy v0.8.5 with some updates, including this fix, soon and update the demo app as well.

It works,thank you so very much for the good work :d

Great work on Twiggy.

How do you incorporate existing CI views into Twiggy.

For example: If I want existing CI views to be the html body and I want headers and footers driven by Twiggy.

You should take a look at Output class: http://ellislab.com/codeigniter/user-guide/libraries/output.html

I’m sure that you could pull something off with

methods.

However, I don’t really recommend using both standard views and twig templates on the same page. Of course, it depends on what you’re trying to accomplish but to me it seems like an overkill.

Nice work !
I’m a bit new to CI and Twig, but achieved to make your twiggy working at least for the demo structure.
What I don’t get is how I can use this to create several “template” folders (not files only).

Actualy the app only work inside “themes/default” folder and I want to be able to select a “template” not by a file but by a folder.

At the end the themes folder would look like :
theme :
- default :
  - index.html.twig
  - layouts :
    - index.html.twig
- my_template :
  - …
- another_template :
  - …

Is this behavior even possible or did I get wrong on the whole template engine mechanism ?
I’m really new to this framework thing so I may be asking dumb questions sorry.

My only controller is home.php, it is set in the config routes, and it looks like :

I was happy to find some function to set the template in the twiggy core file but it didn’t help much. I guess we’re not referring to the same thing with the word “template”. I want it to be able to choose between several WEBSITE template (themes folders) when twiggy look for files inside the themes/default folder.

If you can help here, I’ll appreciate

Hi CreeAll,

I found solution for change theme.

Open file “sparks/Twiggy/0.8.5/libraries/Twiggy.php” and chnage some code in private function _set_template_locations($theme)
line

to

and line

to

Hi,

how to display elapse_time and memory_usage in twig template?

thanks

Duplicate post - please see below

Hey great work on Twiggy.  I’m new to CI and having a bit of trouble figuring out how to implement.  I’ve downloaded your example code from:
Demo (example) application: https://github.com/edmundask/codeigniter-twiggy-demo

I’m having trouble understanding how I should modify a standard CI view to pull a template.

In your demo app, you have the “factory default”  welcome_message view.

It would be very helpful if you could repost the project with the welcome_message view using the twiggy template.

Or… a quick note on what changes are needed to the view / controller to pull the content properly.

Currently I have modified my view to just have the body content and have put the follow code in my welcome controller:

I get the twiggy template rendered and then after the html close tag, the modified welcome_message - which is obviously not right.

Sorry about what I’m sure to be a very obvious oversight and ty for the help.

So a couple things I figured out for all you other newbies.
1) A default non-wamp install of apache does not recognize .htaccess files which are required for most CI demos to remove the index.php.  Editing of the httpd.conf file is required.

2) urls to access the twiggy views in the demo app are:
/articles
/articles/view_with_sidebar

3) Actual twiggy logic for demo is found in:
/application/modules/articles/

4)  Forget about CI views with Twiggy.  Twiggy templates = CI views.

helia_Dar - 24 November 2012 01:35 PM

So a couple things I figured out for all you other newbies.
1) A default non-wamp install of apache does not recognize .htaccess files which are required for most CI demos to remove the index.php.  Editing of the httpd.conf file is required.

2) urls to access the twiggy views in the demo app are:
/articles
/articles/view_with_sidebar

3) Actual twiggy logic for demo is found in:
/application/modules/articles/

4)  Forget about CI views with Twiggy.  Twiggy templates = CI views.

It seems this thread isn’t all that active any more, but just to clarify a bit on these points..

1) Whether .htaccess works or not has nothing to do with WAMP or LAMP, it relies on an Apache specific setting. If your (L/W)AMP stack is not obeying rules set in your .htaccess file, check the AllowOverride directive in your Apache configuration.

3) This is not because of Twiggy, but rather because the example in question uses Wiredesignz’s HMVC modification, you’ll see his files in the /application/third_party/MX/ folder.

4) Don’t forget about default CI Views, Twiggy templates != CI Views. As stated in the Twiggy readme file, it doesn’t replace the default methods, so you can still use them side by side without any problems. For example, for maintenance pages, “still under construction” pages or (if you use them) landing pages.

Hope that helps clarify things a little bit… And of course, happy Twigging.

@Edmundas, hope you’re still watching this thread… I have a question regarding your Twiggy implementation of Twig. I’ve been trying to understand how the ‘_layouts’ folder fits into Twig, but I’m getting slightly confused here.

On your Twiggy page you give the example folder structure as:

Then the ‘index.html.twig’ file outside the ‘_layouts’ folder starts with:

Looking at the Twig documentation (specifically this page), I can’t seem to find any examples of using ‘extends’ to reference a folder, only to reference files. Did you perhaps extend the ‘extends’ side in your implementation? Or am I perhaps missing some important point in the documentation?

Currently I’m running Twiggy with a folder structure of:

Then starting my index.html.twig file with:

This works perfectly for me, but I can’t help but wonder if I’m missing out on some fancy feature here…