Get XOOPS XOOPSXOOPS FAQFAQ ForumsForums NewsNews ThemesThemes ModulesModules
News World of XOOPS Developers Hacks Modules Themes YAXS Archive Submit News

Search

Donat-O-Meter

Make donations with PayPal!
Stats
Goal: $100.00
Due Date: Jun 30
Gross Amount: $25.00
Net Balance: $23.57
Left to go: $76.43

Donations
Anonymous ($15)Jun-14
Anonymous ($10)Jun-10

Learn XOOPS Core

Local Support

Advertisement

XOOPS Code hosted on SourceForge

Cumulus Tag Cloud

2 2.5 2.6 3.0 87 2013 Abuse admin AntiHarvesting AntiMalUser AntiSpam API bags Beats billige black Blocks blue Bootstrap Captcha cell Christmas chronolabs content Conversion demo docek download Dresses editor evden eve facebook floor free herre Honeypot Human IP IPInfoDB jQuery kantor lamps Language log logger Lucire mobile module modules Monster mulberry MyAlbum-p newbb news online PageRank pandora Password Permissions pink Plugin portal preloader Prevention profile project propose Protector publisher Rights rmcommon Room Rotor sale security Server site SmartClone Smarty SOAP Songlist Spam stem Studio tag tags tdmcreate template Theme themes TinyMCE User userlog website Whitepaper Wishcraft xoops Xortify ZendFramework

New Users

Registering user

# 136113

metalgearxd

Welcome to XOOPS!

Archives

News Archives

Mor.Pho.GEN.e.sis 3.0 : The imago takes flight

Posted by kris_fr on 2009/12/14 18:50:00 (6844 reads) | Posted on Themes

Originally we had eggs that we had given Leostotch and Skalpa with Zetareticuli theme, then the larva Mor.Pho.GEN.e.sis by snow77, and after successive moults the larva to reach the nymph, meanwhile, I adapted zetareticuli to give you Zetagenesis now as the Xoops core.

After 3 ½ years of a process of evolving from the XOOPS Design Team and a few tens of thousands of themes online based on this template theme, an Imago comes in the Laboratory XooFoo.org finally to extricate itself from its shell !!

Version 3.0 Mor.Pho.GEN.e.sis fruit of maturity, and possesses a wealth of features and options modularity and customization, which will delight any Xoops user by allowing him to release his creativity with minimal knowledge of languages html, css, javascript or php.
On the first "confused" after a short study you find that it has been designed from a simple logic and is easily adjustable from only a few files.

Download the template theme Mor.Pho.GEN.e.sis --> HERE


Morphogenesis

Installation

Unpack the archive and upload all the folders and files directly into the folder 'themes' of your site

Information

Note 1: To seize the opportunity to add blocks in the footer or the home box (under the header), you must save the file "function.block.php" in yourSite / class / smarty / xoops_plugins /
Note 2: To enjoy the possibility of adding an insert content in the header in home page, you must verify or fill the following line in the file xo_homepage.html: <(if! Xoops_isuser & $ & $ smarty . server.PHP_SELF == '/ index.php')>

  • if your site is at the root of the server, put '/ index.php',
  • if '/ nomdudossier / index.php'

If you have difficulty finding the path, add "() $ smarty.server.PHP_SELF> first line of this file and the information displayed, then remove the line and comments on issues of security

Note 3: You can disable or enable different files (include) or subject area (columns left and right, high and low blocks) by changing values in the file xo_thm_parameters.html
Note 4: Documentation is being drafted and should be published in the first quarter of 2010. But by then, many tips have been published on this theme on the Xoops forum (here or Xoops France).

Acknowledgments

  • Snow77, Skalpa and Leostotch for initial work, Dugris - Burning and Christian for help and tests,
  • Xoops Community for inspiration and suggestions for improvement
  • XOOPS Design Team for its participation in the development and use of this theme template
  • The Afux (Xoops Users French Association) for support in this project.

Credits


Download

Mor.Pho.GEN.e.sis 3.0 is available HERE

Demo

Install the theme on your site, and you will!

Extras

Join the Group Mor.Pho.GEN.e.sis for Xoops on Facebook! and/or become a Fan! and receive the daily news and tips for users of the template theme.



Printer Friendly Page Send this Story to a Friend Create a PDF from the article
Bookmark Me
Bookmark to Google Plus
The comments are owned by the author. We aren't responsible for their content.

Hi kris,

thanks for this new nice theme. I was wonder to try it out but I got this error:
Quote:
Error: Smarty error: [in morphogenesis/xotpl/xo_homepage.html line 43]: syntax error: unrecognized tag 'block' (Smarty_Compiler.class.php, line 590)

I am running XOOPS 2.4.2 on a local Xampp 1.7.0 for windows environment.

I have some problems with translations of core and modules so maybe it the error can due to those problems?

flymirco
Published: 2009/12/14 21:01 • Updated: 2009/12/14 21:01
Hey!
I see you won the battle :D
After two days working with it (started with 3.0b2 I quess) I see nice implementation of morphogenesis :D
well done Kris!
I'm wainting for documentation to build my own themes based on that framework (that morphogenesis is for me).

As we see - that a nice piece of proffessional work with XOOPS theme and system flexibility!
Published: 2009/12/14 21:11 • Updated: 2009/12/14 21:11
I have found the problems.
There are error in morphogenesis/xotpl/xo_homepage.html file at line 43, 50, 55 and more.
It's always the same problem: a
<{block
smarty tag that have to be renamed in
<{$block
every time it gives error.

flymirco
Published: 2009/12/14 21:16 • Updated: 2009/12/14 21:16
Beautifull!

This last weeks, great news and proffesional stuff for xoops.

Superb!
Thanks to all of you!
Published: 2009/12/15 3:39 • Updated: 2009/12/15 3:39
Looks awsome, great work kris_fr :)
Published: 2009/12/15 4:43 • Updated: 2009/12/15 4:43
Thank you all

@ flymirco :
Quote:
To seize the opportunity to add blocks in the footer or the home box (under the header), you must save the file "function.block.php" in yourSite / class / smarty / xoops_plugins /

function.block.php file is in "extras"

xo_parameters.html for show or hide area content zone
<!-- parameters for the positioning of blocks top and bottom -->
    <{* 
Center blocks display order valid values are:  lrc (left right centerlcr (left center rightclr (center left right)    *}>
    <{
assign var=theme_top_order value=lrc}>
    <{
assign var=theme_bottom_order value=lrc}>

<!-- 
Setting this to 0 will remove the display toggle button on all browsers -->
    <{
assign var=theme_left_toggle value=1}>
    <{
assign var=theme_right_toggle value=1}>
    <{
assign var=theme_homepage_toggle value=1}>

<!-- 
Setting this to 0 will remove the display link for view all on all browsers -->    
    <{
assign var=theme_viewall_block value=1}>
    <{
assign var=theme_viewall_content value=1}>
    
<!-- 
Setting this to 0 will remove the display the topheader -->    
    <{
assign var=theme_view_topheader value=1}>
    <!-- for 
remove the display the language choice in topheader-->    
    <{
assign var=theme_view_languagechoice value=1}>    
    <!-- for 
remove the display the searchbar in topheader-->    
    <{
assign var=theme_view_searchbar value=1}>
    <!-- for 
remove the display the userbar in topheader -->    
    <{
assign var=theme_view_userbar value=1}>
    <!-- for 
remove the display the userbar in topheader -->    
    <{
assign var=theme_view_accessibilitybar value=1}>
<!-- 
Setting this to 0 will remove the display the horizontal menu globalnav -->    
    <{
assign var=theme_view_globalnav value=1}>
<!-- 
Setting this to 0 will remove the display the homepage/homebox -->    
    <{
assign var=theme_view_homepage value=1}>
<!-- 
Setting this to 0 will remove the display the left column -->    
    <{
assign var=theme_view_leftcolumn value=1}>
<!-- 
Setting this to 0 will remove the display the right column -->    
    <{
assign var=theme_view_rightcolumn value=1}>
<!-- 
Setting this to 0 will remove the display the topblock content -->    
    <{
assign var=theme_view_topblock value=1}>
<!-- 
Setting this to 0 will remove the display the bottomblock content -->    
    <{
assign var=theme_view_bottomblock value=1}>
<!-- 
Setting this to 0 will remove the display the breadcrumb -->    
    <{
assign var=theme_view_breadcrumb value=1}>
<!-- 
Setting this to 0 will remove the display the socialbookmark bar -->    
    <{
assign var=theme_view_socialbookmark value=1}>
<!-- 
Setting this to 0 will remove the display the blockfooter in footer -->    
    <{
assign var=theme_view_blockfooter value=1}>
<!-- 
Setting this to 0 will remove the display the w3cblock in footer -->    
    <{
assign var=theme_view_w3cblockfooter value=1}>
<!-- 
Setting this to 0 will remove the display the baradmin -->    
    <{
assign var=theme_view_baradmin value=1}>


- you can now customize css Individual blocks
id="xo-block<{$block.module}><{$block.id}>"

done (exemple) id="xo-blocknews14"

and more, more ...
Published: 2009/12/15 4:55 • Updated: 2009/12/15 4:55
Hello!

Great work!
Published: 2009/12/15 7:00 • Updated: 2009/12/15 7:04
Block customization is really fine and perfect solution!
Published: 2009/12/15 8:06 • Updated: 2009/12/15 8:06
great work , congratulation
Published: 2009/12/15 8:44 • Updated: 2009/12/15 8:44
Quote:
This last weeks, great news and proffesional stuff for xoops.

Yes, a LOT of good things coming lately out of our designers' labs!!!

The Inspire themes from Insraq, editable blocks from Aph3x, and now Mor.Pho.GEN.e.sis 3.0!!!

It's so exciting to see all of this creative and innovative work being developed for XOOPS!!!

Kris, very nice work! Now we need a "Morpho Theme builder" similar to Artisteer
Published: 2009/12/15 8:49 • Updated: 2009/12/15 8:49
Hmm it says the archive is corrupted...
Published: 2009/12/15 10:22 • Updated: 2009/12/15 10:22
very good the work, congratulations
Published: 2009/12/15 11:41 • Updated: 2009/12/15 11:41
@ deka87 : may be ... use 7zip
Published: 2009/12/15 11:43 • Updated: 2009/12/15 11:43
Good work!

I have 2 problems/questions:
First:
Why use id="xo-block<{$block.module}><{$block.id}>" ?
Why not id="xo-block-<{$block.id}>" ?
I do think having the block wrapped with a unique id is very important but, the id of the block must be simple to get using javascript. I'm thinking in front page editing, I'm thinking in ajax calls where the id of the div is passed as parameter to a php file that will extract the blockid and deliver the block form to the javascript.

Second:
Themes should use XOOPS API to include information into the header like css or js. It would be nice to see some of $xoTheme->addScript() or $xoTheme->addStylesheet(). Notice that using API we can avoid duplication of files. If one module decides to include xoops.css, we will get 2 files loaded because one of them is hardcoded on the theme.

Thanks :)
Published: 2009/12/15 17:21 • Updated: 2009/12/15 17:21
hi trabis,

1.1) the module name is just to show the name of the module reference in the css sheet and the source code of the page.
xo-block13: what module? - xo-blocknews13: oh yes, News module!
1.2) in the template I tried to minimize the javascript, then the web designer to see if he wants dojo, jquery, mootools, etc ... this is not for me to impose a choice but to him or his client
1.3) I assume that the user has more than basic knowledge in html as php, so no php in the template (many XOOPS users do not have concepts in php - by experience support forums)
2) why a module inserted xoops.css when it is already in all themes? development error of the module?
Published: 2009/12/15 17:44 • Updated: 2009/12/15 17:44
Hi again Kris,

1) If my php file gets $var = 'xo-blocknews13' it will be difficult to extract the blockid from it. $var='xo-block-13' is straight forward. If you want to keep dirname there please make it like this: $var = 'xo-block-news-13'

1.2) I can make a module that looks into the output and adds javascript to make front block edit possible, I just need to be able to identify the blocks ids. I was not asking you to make front block editing, I just need you to let the door open for it.

1.3) There is little difference between
<{assign var=theme_top_order value=lrc}>
<{
assign var=theme_bottom_order value=lrc}>

and
$xoopsTpl->assign('theme_top_order''lrc');
$xoopsTpl->assign('theme_bottom_order''lrc');


2) I said xoops.css as I could have said browse.php?Frameworks/jquery/jquery.js. This is not important if the js or css is inside the theme package because modules will not use them, but if we are referring to a core/Framework/common file then it is important to use API to load it. If in the future we decide to load xoops.css inside theme.php class, we will not have problems with morphogenisis themes!

I heard someone asking preloads for themes, it would not be bad idea.
Published: 2009/12/15 18:15 • Updated: 2009/12/15 18:15
Hi everyone,

With this developed and customisable theme, wouldn't it be possible to extand the customisation on the admin part.

I mean record the data (columns width and height, background colors, logo,...) in the database (ask css files to look datas in the db), so it could be charge with other datas.

This would make easier the customisation by newbies like me lol!

By the way, i think it would be a first for a CMS!

Best regards,

Paco
Published: 2009/12/16 4:26 • Updated: 2009/12/16 4:26
Quote:
Why use id="xo-block<{$block.module}><{$block.id}>" ?
It should be:
id="xo-block-<{$block.module}>-<{$block.id}>".
This allows styling for all blocks of one module etc.
Published: 2009/12/16 9:43 • Updated: 2009/12/20 18:32
Quote:
I heard someone asking preloads for themes, it would not be bad idea.


That was me .

Still hoping it will be in the next XOOPS version .

Greets Dylian.
Published: 2009/12/16 11:26 • Updated: 2009/12/16 11:26
Language persian for Morphogenesis 3.0.1 is released (thanks Voltan ) - download files here --> http://tutos.xoofoo.org/modules/mydow ... /visit.php?cid=40&lid=282
Published: 2009/12/17 10:32 • Updated: 2009/12/17 10:32
Nice theme, thx
Published: 2009/12/20 10:40 • Updated: 2009/12/20 14:23
Mor.Pho.GEN.e.sis version 3.1 beta 1 is available here --> https://sourceforge.net/projects/xoofo ... nesis_v3.1b1.zip/download

changelog:
============================
Version 3.1 beta 1 ( for XOOPS 2.4.x )
============================
- Add an extra SMARTY variable $xoops_themeurl - (kris / kaifulee team)
- Add an extra SMARTY variable $xoops_module_theme - (kris / kaifulee team)
- If a module has its own css (located themes/themename/modules/dirname/style.css), append it to $xoops_module_header - (kris / kaifulee team)
- If a module defines its own canvas template (located themes/themename/modules/dirname/xo_canvas.html), take it; otherwise the default canvas (themes/themename/xotpl/xo_canvas.html) is used - (kris / kaifulee team)
- Add new include file xo_page.html for XOOPS basics columns (kris)
- Add personalization exemple for contact module and display userinfo (kris)
- Search engine optimization - see http://www.xoops.org/modules/smartfaq/faq.php?faqid=362 (kris)
Published: 2009/12/27 10:11 • Updated: 2009/12/27 10:12
Thanks Kris & kaifulee team, a lot of new features !

Just a question about $xoops_module_header : how can we use it ? Could you give an example ? And if we use such method to override a module stylesheet, XOOPS cache works properly now (*) ?

Thanks again


* : there is an issue if you active cache on a module, overrided stylesheets are forgotten
Published: 2009/12/28 5:05 • Updated: 2009/12/28 5:42
I think I owe you some explanations on the new innovation of version 3.1 of Mor.Pho.GEN.e.sis.
- With the overload of existing themes, a style sheet style.css file in a single module overload is not taken into account at least to incorporate it via a template overload; style.css sheet now lost in this record is taken into account
- You can also override a theme per se, and there instead of a long speech, I prefer to give you an example (download here)
* Unzip the archive and put the file "news" in the subject overload (tonsite/themes/tonthememorphogenesis3.1/modules /) - of course you need the module news on your site
* Now go to the news module ... and enjoy

This surcharge is based on the theme xforange gray v3 studioC by our friend Burning revived (see article on xoops.org)

to see the slight changes I made for this test, simply compare the files with WinMerge by example

@ + And good fun
Published: 2009/12/28 5:57 • Updated: 2009/12/28 5:57
Thanks a lot !
I will try as soon as possible !

I'm building a new theme with Morphogenesis... and I was thinking that would be nice to have bigger user icons in /docs (I need 32px size instead of 16px, and designers could reduce it without damage : 24px, 16px ...). Just an idea

Click to see original Image in a new window
Click to see original Image in a new window
Click to see original Image in a new window
Click to see original Image in a new window
Click to see original Image in a new window
Click to see original Image in a new window
Click to see original Image in a new window


Download zip
Published: 2009/12/28 7:08 • Updated: 2009/12/28 7:09
http://www.xoofoo.org/uploads/icons_user_16.zip
Published: 2009/12/28 7:26 • Updated: 2009/12/28 7:26
Mor.Pho.GEN.e.sis 3.1 with dynamic Css Menus --> HERE
Published: 2009/12/29 11:01 • Updated: 2009/12/29 11:01
Version 3.1.3 is released

============================
Version 3.1.3 ( for XOOPS 2.4.x )
============================
- Add new smarty balise <{$xoops_module_themeurl}> for --> siteurl/themes/themename/modules/modulename/ - (kris)

============================
Version 3.1.2 ( for XOOPS 2.4.x )
============================
- Add style sheet reset.css - (kris)

============================
Version 3.1.1 ( for XOOPS 2.4.x )
============================
- Add news class in extras.css for display div in table - (kris)
- encode xo_homepage.html to utf 8 sans bom (kris)
- add french translation in iso, utf8 and numeric encodage


NOTE : Now you have 4 news smarty balises for use in this theme
<{$canvas_template}> for --> themes/themename/modules/modulename/xo_canvas.html
<{$xoops_themeurl}> for --> urldusite/themes/themename
<{$xoops_module_theme}> for --> themename/modules/namemodule
<{$xoops_module_themeurl}> for --> siteurl/themes/themename/modules/modulename/
Published: 2010/1/12 17:25 • Updated: 2010/1/12 17:26