11
bitcero
Re: Custom PHP Page with no header and footer
  • 2015/2/9 7:14

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


All is possible! :) The solution is in two steps: You code is good, but change the last line.
<?php  

include("../../mainfile.php");  
include(
XOOPS_ROOT_PATH."/header.php");  

$meta_keywords "";  
$meta_description "";  
$pagetitle "";  

if(isset(
$xoTheme) && is_object($xoTheme)) {  
    
$xoTheme->addMeta'meta''keywords'$meta_keywords);  
    
$xoTheme->addMeta'meta''description'$meta_description);  
} else {    
// Compatibility for old Xoops versions  
    
$xoopsTpl->assign('xoops_meta_keywords'$meta_keywords);  
    
$xoopsTpl->assign('xoops_meta_description'$meta_description);  
}  

$xoopsTpl->assign('xoops_pagetitle'$pagetitle);  

//this will only work if your theme is using this smarty variables  
$xoopsTpl->assign'xoops_showlblock'0); //set to 0 to hide left blocks  
$xoopsTpl->assign'xoops_showrblock'0); //set to 0 to hide right blocks  
$xoopsTpl->assign'xoops_showcblock'1); //set to 0 to hide center blocks  
?>  

htmml or php content  

<?php  
echo $xoopsTpl->fetch'your_template_path' );
?>
Then, create a template with all styles and content that you wish, but remember to provide all HTML structure:
<!DOCTYPE html>
<
html>
  <
head>...</head>
  <
body>...</body>
</
html>
Of course this solution is valid only with Smarty.



12
bitcero
Re: Not seeing any changes to my templates
  • 2015/1/29 14:38

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


The solution (in most cases) is to delete the appropiate cached template from xoops_data/caches/smarty_cache. IN some cases, even when cache is diabled, Smarty creates a cache for some templates (I have not investigate why, but does it)



13
bitcero
Ethernial: a new freemium theme for XOOPS
  • 2014/12/24 1:12

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


Introducing a new theme mabe by me: Ethernial

Ethernial theme

Ethernial is a modern and good looking theme designed using xThemes and Bootstrap. It is inspired on other theme by HTML5 UP.

Features:

  • A full featured configuration panel.
  • Automatically compiling of less files that build bootstrap and theme styles.
  • Customization of colors and images (general appearance).
  • Support of custom CSS code via configuration (forget to modify files directly to customize certain parts of theme).
  • Fully integration with MyWords, Professional Works and QuickPages
  • A totally new block for twitter feed (using the rmcommon blocks sytem).
  • You can choose between show blocks at left or right of theme.
  • Two blocks zones: sidebar and footer.
  • A lot of more things...

Requirements

If you wish to use Ethernial, then some components are required:

  1. Common Utilities
  2. xThemes
  3. MyWords
  4. Professional Works
  5. QuickPages
  6. Advanced Forms
  7. and, of course, XOOPS

View Demo Descargar

View post in spanish




14
bitcero
Re: PRECHECK resursion in protector
  • 2014/12/15 19:47

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


Due to nature of rmcommon, it can not be hidden from active menus. If you wish to use the block "main menu" then is preferable to hide rmcommon directly from the template of this block.

You can edit the file "modules/system/templates/blocks/system_block_mainmenu.html" and change the content from this:

<div id="mainmenu">
    <
class="menuTop <{if !$block.nothome}>maincurrent<{/if}>" href="<{xoAppUrl }>" title="<{$block.lang_home}>"><{$block.lang_home}></a>
    <!-- 
start module menu loop -->
    <{foreach 
item=module from=$block.modules}>
        <
class="menuMain <{if $module.highlight}>maincurrent<{/if}>" href="<{$xoops_url}>/modules/<{$module.directory}>/" title="<{$module.name}>"><{$module.name}></a>
        <{foreach 
item=sublink from=$module.sublinks}>
            <
class="menuSub" href="<{$sublink.url}>" title="<{$sublink.name}>"><{$sublink.name}></a>
        <{/foreach}>
    <{/foreach}>
    <!-- 
end module menu loop -->
</
div>


to this:

<div id="mainmenu">
    <
class="menuTop <{if !$block.nothome}>maincurrent<{/if}>" href="<{xoAppUrl }>" title="<{$block.lang_home}>"><{$block.lang_home}></a>
    <!-- 
start module menu loop -->
    <{foreach 
item=module from=$block.modules}>
    <{if 
$module.dirname!='rmcommon'}>
        <
class="menuMain <{if $module.highlight}>maincurrent<{/if}>" href="<{$xoops_url}>/modules/<{$module.directory}>/" title="<{$module.name}>"><{$module.name}></a>
        <{foreach 
item=sublink from=$module.sublinks}>
            <
class="menuSub" href="<{$sublink.url}>" title="<{$sublink.name}>"><{$sublink.name}></a>
        <{/foreach}>
    <{/if}>
    <{/foreach}>
    <!-- 
end module menu loop -->
</
div>





15
bitcero
Re: error publisher block timthumb
  • 2014/12/5 13:29

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


If it is possible, avoid the use of timthumb: TimThumb is No Longer Supported or Maintained



16
bitcero
Re: Common Utilities Troubleshooting
  • 2014/11/30 3:18

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


rmcommon needs PHP 5.4.

You can disable the inline debug if you wish.



17
bitcero
Re: i'm working an a standard module skeleton
  • 2014/11/18 18:51

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


Hi everybody.

For several recent projects, I've been using the MVC approach included in rmcommon. The biggest project where I've applied this was an ERP created entirely in XOOPS, that consists of several modules. All those modules were created from scratch, using rmcommon and MVC. The main idea is that, with this approach, the required time to create a module is smaller that traditional way. Also, by using AJAX, is possible to bring a better experience to users.

I've recently wrote an article with a brief explanation about MVC in Common Utilities but it is in Spanish.

I think that this will be a very important discussion if the result bring to XOOPS modules a new life.



18
bitcero
Re: Asking for your opinion about QuickPages
  • 2014/7/20 19:12

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


@olivee: thanks for report about sql file, this bug is corrected.

The code is used in htaccess file and allows to have short urls for a single page. This means that you can acces to a specific page with an URL like next:

http://yoursite.com/custom-path

or in other cases:

http://yoursite.com/pages/custom-path

QuickPages make the changes for you when the server is configured for this. In other cases you need to modify it manually.




19
bitcero
Re: Asking for your opinion about QuickPages
  • 2014/7/20 19:08

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


Quote:

What do you think about merging your common utilities and advanced forms to the new xoops version. The development is in progress and it would be really cool to see your hack merged to xoops.
It would be a huge improvement for user experience.


I'm trying to integrate rmcommon with XOOPS 2.6... a lot of work is needed.



20
bitcero
Re: Asking for your opinion about QuickPages
  • 2014/7/18 21:31

  • bitcero

  • Quite a regular

  • Posts: 318

  • Since: 2005/11/26


@heyula: Can you post the version of XOOPS, Common Utilities and any other detail that can help?




TopTop
« 1 (2) 3 4 5 ... 7 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

54 user(s) are online (38 user(s) are browsing Support Forums)


Members: 0


Guests: 54


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jan 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits