XOOPS Web Application System

Bootnewage CPanel theme (Beta release)

Tue, 31 Mar 2015 05:10:00 +0000

I am happy to introduce a new CPanel (Admin) theme for XOOPS, completely rewritten with Bootstrap, in order to provide visibility and compatibility with different mobile devices.

It is important to stress that unfortunately, with versions of XOOPS 2.5.x that support Bootstrap, this Admin theme may not work properly. Therefore this Beta version should be tested first locally, before using it in a production site.

I have changed many file in the System module, in addition to many other Core files, so it is necessary to do the tests on a fresh installation of XOOPS on your localhost, because if there is incompatibility with this new code, you're not risking anything.

However, even the Default theme will be changed, to avoid any problems.

This below is a screenshot of the theme that can be modified in various colors just like the default theme.

600) this.width=600" />

Libraries used:
- bootstrap.css 3.3.2
- bootstrap.theme.css 3.3.2
- bootstrap.min.js 3.3.2
- jquery.min.js 1.11.2
- jquery-ui.min.js 1.10.4

As I wrote in this thread for some problems, you might find difficulty with some features.

I must point out that in the package there are other themes, in addition to the default, but they are not complete like this one. You can still edit them to your liking in the expectation that we can use in production.

See all collaction on Flickr

Download Pack

To report issues or provide feedback, please go to this thread.

Headline News Publisher

Sat, 27 Sep 2014 14:23:41 +0000

600) this.width=600" />

theme.html Code :

 <linkÂ href="<{xoImgUrlÂ css/mansetx.css}>"Â type="text/css"Â rel="stylesheet"Â />Â Â  
<scriptÂ type="text/javascript"Â src="<{xoImgUrlÂ js/mansetx.js}>">script> 
<scriptÂ type="text/javascript"Â src="<{xoImgUrlÂ js/jquery-1.11.1.js}>">script>

theme.html add :

<{includeqÂ file="$theme_name/slidetpublisher.html"}>

slidetpublisher.html code :

 <{php}> 
include_onceÂ XOOPS_ROOT_PATHÂ .Â '/modules/publisher/include/common.php'; 
$publisherÂ =&Â PublisherPublisher::getInstance(); 
$mytsÂ =&Â MyTextSanitizer::getInstance(); 
$itemsObjÂ =Â $publisher->getHandler('item')->getItems($limitÂ =Â 6,Â $startÂ =Â 0,Â array(_PUBLISHER_STATUS_PUBLISHED),Â -1,Â $sortÂ =Â 'datesub',Â $order='DESC',Â '',Â true,Â $criteriaÂ =Â null,Â true); 
$totalItemsÂ =Â count($itemsObj); 
 
globalÂ $items; 
$itemsÂ =Â array(); 
ifÂ ($itemsObj)Â { 
Â Â Â Â Â Â Â Â forÂ (Â $iÂ =Â 0;Â $iÂ <Â $totalItems;Â $i++Â )Â { 
 
Â Â Â Â Â Â Â Â Â Â Â Â $newItems['itemid']Â Â Â Â Â Â Â =Â $itemsObj[$i]->itemid(); 
Â Â Â Â Â Â Â Â Â Â Â Â $newItems['title']Â Â Â Â Â Â Â Â =Â $itemsObj[$i]->title(); 
Â Â Â Â Â Â Â Â Â Â Â Â $newItems['body']Â Â Â Â Â Â Â Â Â =Â $itemsObj[$i]->body(); 
Â Â Â Â Â Â Â Â Â Â Â Â $newItems['votes']Â Â Â Â Â Â Â Â =Â $itemsObj[$i]->votes(); 
Â Â Â Â Â Â Â Â Â Â Â Â $newItems['image']Â Â Â Â Â Â Â Â =Â XOOPS_URLÂ .Â '/uploads/blank.gif'; 
Â Â Â Â Â Â Â Â Â Â Â Â $imagesÂ =Â $itemsObj[$i]->getImages(); 
Â Â Â Â Â Â Â Â Â Â Â Â ifÂ (is_object($images['main']))Â { 
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â $newItems['image']Â =Â XOOPS_URLÂ .Â '/uploads/'Â .Â $images['main']->getVar('image_name'); 
Â Â Â Â Â Â Â Â Â Â Â Â } 
Â Â Â Â Â Â Â Â $items[]Â =Â $newItems; 
Â Â Â Â } 
} 
<{/php}> 
Â Â Â Â Â Â Â Â <divÂ id="mansetx"> 
Â Â Â Â Â Â Â Â Â Â Â Â <{php}> 
Â Â Â Â Â Â Â Â foreachÂ (Â $GLOBALS['items']Â asÂ $myrowÂ ) 
Â Â Â Â Â Â Â Â { 
Â Â Â Â Â Â Â Â $GLOBALS['xoopsTpl']->assign('itemid',Â $myrow['itemid']); 
Â Â Â Â Â Â Â Â $GLOBALS['xoopsTpl']->assign('title',Â $myrow['title']); 
Â Â Â Â Â Â Â Â $GLOBALS['xoopsTpl']->assign('body',Â $myrow['body']); 
Â Â Â Â Â Â Â Â $GLOBALS['xoopsTpl']->assign('votes',Â $myrow['votes']); 
Â Â Â Â Â Â Â Â $GLOBALS['xoopsTpl']->assign('image',Â $myrow['image']); 
<{/php}> 
Â Â Â Â Â Â Â Â <divÂ id="mansetx-img"> 
Â Â Â Â Â Â Â Â Â Â Â Â <aÂ href="<{$xoops_url}>/modules/publisher/item.php?itemid=<{$itemid}>"><imgÂ width="720"Â height="315"Â src="<{$image}>">a> 
Â Â Â Â Â Â Â Â div> 
Â Â Â Â Â Â Â Â Â <{php}> 
Â Â Â Â Â Â Â Â } 
<{/php}>Â  
Â Â Â Â Â Â Â Â <divÂ id="mansetx-selector"> 
Â Â Â Â Â Â Â Â Â Â Â Â <ul> 
Â Â Â Â Â Â Â Â Â Â Â Â ul> 
Â Â Â Â Â Â Â Â div> 
div>

Demo :

http://estetikameliyatmerkezi.com/xoopson/

Hasta YataklarÄ±

Facebook comments added to Publisher module version 1.02

Sat, 27 Sep 2014 14:23:32 +0000

Hi,
I did it, I added the fecebook comment in publisher module version 1.02

1. I Work with publisher version 1.02
2. and the theme xbootstrap version 1.02
3. I have to prepare a winzip if you want

If you want to see how it looks, takes a look here
CLICK HERE

Regards
DAVID

500) this.width=500" />

TDMDownloads Block Views

Mon, 13 May 2013 21:19:36 +0000

TDMDownloads 1.6 :
------------------------------
tdmdownloads_block_top.html
tdmdownloads_block_new.html
------------------------------

700) this.width=700" />

Demo :
http://www.programgezgini.com/

Downloads :
http://www.programgezgini.com/modules/TDMDownloads/singlefile.php?lid=1184

XoopsFaq / jQuery Plugin: fancy FAQs

Mon, 25 Mar 2013 12:56:33 +0000

605) this.width=605" />

Xoops Faq view

scripts folder / modules/xoopsfaq/templates
images folder / modules/xoopsfaq/images
xoopsfaq_category.html / modules/xoopsfaq/templates

Download : https://sourceforge.net/projects/xoopstr/files/Hack/

Demo : http://evsad.org.tr/modules/xoopsfaq/index.php?cat_id=1

Publisher News Views - Hack

Sun, 24 Mar 2013 22:53:16 +0000

The team on Xoops-tr.com did some improvements in the Publisher, improving on the View, and we wanted to share with all XOOPS users.

Big thanks to Trabis once again for this module.

publisher_display_wfsection.html

Ekran GÃ¶rÃ¼ntÃ¼leri / Screenshots :

Stil - 1 :

300) this.width=300" />

Stil - 2 :

300) this.width=300" />

Demo : http://evsad.org.tr/modules/publisher/

Download : http://www.programgezgini.com/modules/TDMDownloads/singlefile.php?lid=1149

Amazon EC2 and Elastic Load Balancing with XOOPS (whitepaper)

Mon, 01 Oct 2012 03:00:00 +0000

Amazon EC2 and Elastic Load Balancing with XOOPS
Whitepaper by Simon Roberts (of Sydney) - wishcraft

Download Whitepaper: [url=http://code.google.com/p/chronolabs/downloads/detail?name=XOOPS%20and%20Amazon%20EC2%20with%20ELB%20Services.pdf]XOOPS and Amazon EC2 with ELB Services.pdf[url] - 100Kb

Contribution Notices
I would like to thank the following people and organisations for their assistance with the Amazon ec2 and subset of systems, without their institutive understanding and association with Amazon this technical whitepaper would not exist.

ICE Systems:
Quote:

I would like to thank for the establishment of the EC2 cloud in this instance, Peter Barganski from ICE System for his ability to navigate and configure the Amazon cloud. ICE System's is a reseller and Amazon Partner and have provided me with quick and fast responsive and adaptive environment needed for the Lunchalot.com system we are designing.

lunchalot.com:
Quote:

Secondly I would like to thank my employer, lunchalot.com (contact@lunchalot.com) for so quickly choosing XOOPS as the framework to move their existing web infrastructure over to and in particular Richard the CEO enthusiasm for moving the Proof-of-concept web infrastructure into XOOPS and the team for all their hours testing.

Preface
This whitepaper is to describe the process involved in defining Amazon's EC2 with Elastic Load Balancing with the XOOPS Portal System. It is designed to be used with XOOPS 2.5 or later, and the associate files are provided as per GNU licensing of the source. ELB or Elastic Load Balancing within Amazon's EC2 cloud, is the process, where an ELB service will start up as per requirement instances of a website image supporting your website.

When ELB is in place, the Amazon cloud will start up and direct traffic to multiple instances of your website as per the traffic requirement of the site. This all depends on what sort of instances you are using and its capabilities. All the files provided have been tested and are designed to be used with Amazons Ubuntu services.

This sort of service will be required with a site that has a heavy traffic requirement that a single VPS or Private server cannot cope with and when you need multiple services. Why would you use Amazon to do this, well I will quote Peter from ICE Systems on this that ELB services until Amazon made them available where finitely unaffordable and out of reach of even the most durable business intake. As the costs of installing and hosting the services manually where just unjustifiable for most businesses.

This white paper will concentrate on the XOOPS system itself and preparing the CMS/Portal system for the Amazon EC2 environment with ELB in place, some of the systems it describe you will either have to research or employ someone like ICE systems to deploy for you as they contain information which may vary between installations and environment as well as being outside the scope of the documents description.

Anything which is unique to the system this was designed on due to intellectual property rights have been omitted there will be notation in the document as designed or put in generalised terms of reference for use in your own systems.

JQuery UI datepicker

Thu, 28 Jun 2012 12:48:23 +0000

Some time ago on my site, we talked about inserting a plugin datetimepicker that you can insert into a class on xoops. In this news I announce that I have created a special class in the folder class/xoopsform as formdatepicker.php. The result is being able to delete many files from the old calendar, and use a simple method call using the id #datepicker and using the datepicker plugin of jquery datepicker.js
Â
A simple example shows images:
300) this.width=300" />

300) this.width=300" />

300) this.width=300" />

will receive the form by clicking on the icon to the right of the text field, if the icon is activated, or just click in the text field to display the calendar ui jquery.

Read Original News

Solving ajax giving cross-domain error or responding empty

Fri, 09 Mar 2012 18:23:20 +0000

When assigning XOOPS_URL to a javascript variable in eighter preloads or specific pages.

Most often the browser will deny your request and return only an empty respond. But not give error. This can be seen in FireBug's console when the requests is returning code "200 OK" but text is in red color = empty result. Very annoying

The problem is between Xoops Cookie and browser. I noticed this when being logged in to a xoops page and closing the page without logging out. When re-opened the ajax running in my preloads (in this case XIM and Smallworld) was denying sending messages or posting to the wall.

Also this is a problem if you log out from http://domain.com and open http://www.domain.com.

There are as I see this 2 solutions.

1) Everytime you finish browsing do log out.

Another solution is to define the javascript var used in ajax requests according to actual browser adress.

Add a function to your page (if you add to include/functions.php remember to include this page in preloads or the page your working on)

 /** 
Â Â Â Â Â *Â @GetÂ urlÂ ofÂ smallworld 
Â Â Â Â Â *Â @returnsÂ string 
Â Â Â Â Â */Â  
Â Â Â Â functionÂ smallworld_getHostRequest()Â  
Â Â Â Â { 
Â Â Â Â Â Â Â Â $protocolÂ =Â strpos(strtolower($_SERVER['SERVER_PROTOCOL']),'https')Â ===Â FALSEÂ ?Â 'http'Â :Â 'https'; 
Â Â Â Â Â Â Â Â $hostÂ Â Â Â Â =Â $_SERVER['HTTP_HOST']; 
Â Â Â Â Â Â Â Â $scriptÂ Â Â =Â $_SERVER['SCRIPT_NAME']; 
Â Â Â Â Â Â Â Â $paramsÂ Â Â =Â $_SERVER['QUERY_STRING']; 
Â Â Â Â Â Â Â Â $currentUrlÂ =Â $protocolÂ .Â '://'Â .Â $host; 
Â Â Â Â Â Â Â Â returnÂ $currentUrl; 
Â Â Â Â }

In your page reset the var like this

 //Â CheckÂ ifÂ requestÂ urlÂ isÂ withÂ wwwÂ orÂ without 
Â Â Â Â Â Â Â Â globalÂ $xoTheme; 
Â Â Â Â Â Â Â Â $urltestÂ =Â smallworld_getHostRequest(); 
Â Â Â Â Â Â Â Â $xoops_urlÂ =Â XOOPS_URL; 
Â Â Â Â Â Â Â Â ifÂ (!strstr($urltest,Â 'www.'))Â { 
Â Â Â Â Â Â Â Â Â Â Â Â $xoops_urlÂ =Â str_replace(Â 'www.',Â '',Â $xoops_urlÂ ); 
Â Â Â Â Â Â Â Â } 
 
Â Â Â Â Â Â Â Â $scriptÂ =Â "varÂ smallworld_urlÂ =Â '"Â .Â $xoops_urlÂ .Â "/modules/smallworld/"Â .Â "';n"; 
Â Â Â Â Â Â Â Â $xoTheme->addScript('','',$script);

The var smallworld_url will now be according to your browser adress and this way not result in ajax cross-browser error.

Social Media quick tutorial for XOOPS

Sat, 03 Mar 2012 11:07:13 +0000

First of all, you are more than welcome to use any of this, most of what I've done was pieced together from my own bug/debug process. I use everything here on my news website at http://kbkw.com I think I included everything, but please feel free to contact me if you have questions. This could all be seen as continuation of this article at https://xoops.org/modules/news/article.php?storyid=6044 META I add the following to my Meta tags (In the template)

 <metaÂ property="og:type"Â content="article"/> 
Â Â <metaÂ property="og:locale"Â content="en_US"Â /> 
Â Â <metaÂ property="og:image"Â content="<{$xoops_url}>/YOURÂ LOGO.png"Â /> 
Â Â <metaÂ property="og:site_name"Â content="<{$xoops_sitename}>"/> 
Â Â <metaÂ property="fb:admins"Â content="FBÂ ADMINSÂ FORÂ THEÂ SITE"/>

I add some If/Then statements that will populate other facebook values IF we're viewing a story. (IF the story.hits variable is empty then we're not viewing an article)

 <{ifÂ $story.hitsÂ !=''}> 
Â Â Â <metaÂ name="description"Â content="<{$story.news_title|strip_tags:false}>Â :Â <{$story.text|strip_tags:false|truncate:120:"..."}>"Â /> 
Â Â Â <metaÂ property="og:description"Â content="<{$story.text|strip_tags:false|truncate:120:"..."}>"Â /> 
Â Â Â <metaÂ property="og:title"Â content="<{$story.news_title|strip_tags:false|truncate:120:"..."}>"/> 
Â Â Â <metaÂ property="og:url"Â content="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â />

Same as above, but for the debaser module

 <{elseifÂ $addinfoÂ !=Â ''}> 
Â Â Â <metaÂ name="description"Â content="<{$addinfo|strip_tags:true|truncate:220:"..."}>"Â /> 
Â Â Â <metaÂ property="og:description"Â content="<{$addinfo|strip_tags:true|truncate:220:"..."}>"Â /> 
Â Â Â <metaÂ property="og:title"Â content="<{$title}>"/> 
Â Â Â <metaÂ property="og:url"Â content="<{$xoops_url}>/modules/debaser/singlefile.php?id=<{$id}>"Â />

This uses news 1.65's "Select a picture to attach to the news"

 <{ifÂ $articlePictureÂ !=Â ''}> 
Â Â Â Â Â Â Â <metaÂ property="og:image"Â content="<{$articlePicture}>"Â /> 
Â Â Â Â Â Â Â <{/if}>

then from here down we populate variables for the "rest of the pages," and close out our IF statement

 <{else}> 
Â Â <metaÂ name="description"Â content="<{$xoops_pagetitle}>,Â <{$xoops_meta_description}>"Â /> 
Â Â <metaÂ property="og:title"Â content="<{$xoops_pagetitle}>"/> 
Â <{/if}>

lastly I add keywords because facebook pulls this meta before it's own for some reason..

<metaÂ name="keywords"Â content="<{$xoops_pagetitle}>,Â <{$xoops_meta_keywords}>"Â />

TEMPLATES Now in the news_item.html template I add a check for the proper topic:

<{ifÂ $story.topic_title|strip_tags:falseÂ ==Â "LocalÂ News"}>

Followed by my "social bar"

  
<divÂ class="addthis_toolboxÂ addthis_default_styleÂ "> 
Â Â <aÂ class="addthis_button_facebook_like"Â fb:like:layout="button_count"Â addthis:url="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â addthis:title="<{$story.news_title|strip_tags:true}>">a> 
<aÂ class="addthis_button_tweet"Â addthis:url="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â addthis:title="<{$story.news_title|strip_tags:true}>">a> 
<aÂ class="addthis_button_google_plusone"Â addthis:url="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â addthis:title="<{$story.news_title|strip_tags:true}>"Â g:plusone:size="medium">a> 
 
<{ifÂ $articlePictureÂ !=Â ''}> 
Â Â <aÂ href="http://pinterest.com/pin/create/button/?url=<{$xoops_url}>/modules/news/article.php?storyid%3D<{$story.id}>&media=<{$articlePicture}>&description=<{$story.news_title|strip_tags:false}>Â -Â <{$story.text|strip_tags:false|truncate:320:"..."}>"Â class="pin-it-button"Â count-layout="horizontal">PinÂ Ita> 
Â Â Â Â <{else}> 
Â Â Â Â Â Â Â Â <aÂ href="http://pinterest.com/pin/create/button/?url=<{$xoops_url}>/modules/news/article.php?storyid%3D<{$story.id}>&media=<{$xoops_url}>/logo.png&description=<{$story.news_title|strip_tags:false}>Â -Â <{$story.text|strip_tags:true|truncate:320:"..."}>"Â class="pin-it-button"Â count-layout="horizontal">PinÂ Ita> 
<{/if}> 
 
Â Â <aÂ class="addthis_counterÂ addthis_pill_style"Â addthis:url="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â addthis:title="<{$story.news_title|strip_tags:true}>">a> 
div> 
 
Â Â <scriptÂ type="text/javascript"Â src="http://s7.addthis.com/js/250/addthis_widget.js#pubid=YOURÂ PUBÂ ID"Â addthis:url="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"Â addthis:title="<{$story.news_title|strip_tags:true}>">script> 
Â Â

By adding this in the news_item template instead of _article, You see the social icons at the bottom of every story when viewing the entire topic - and the links track through to the stories, so you could "like" every story on a page with a few clicks. **Note: Pinterest requires this additional js at the top of the page (I put mine in both news_index.html and news_article.html

 <scriptÂ type="text/javascript"> 
(function()Â { 
Â Â Â Â window.PinItÂ =Â window.PinItÂ ||Â {Â loaded:falseÂ }; 
Â Â Â Â ifÂ (window.PinIt.loaded)Â return; 
Â Â Â Â window.PinIt.loadedÂ =Â true; 
Â Â Â Â functionÂ async_load(){ 
Â Â Â Â Â Â Â Â varÂ sÂ =Â document.createElement("script"); 
Â Â Â Â Â Â Â Â s.typeÂ =Â "text/javascript"; 
Â Â Â Â Â Â Â Â s.asyncÂ =Â true; 
Â Â Â Â Â Â Â Â ifÂ (window.location.protocolÂ ==Â "https:") 
Â Â Â Â Â Â Â Â Â Â Â Â s.srcÂ =Â "https://assets.pinterest.com/js/pinit.js"; 
Â Â Â Â Â Â Â Â else 
Â Â Â Â Â Â Â Â Â Â Â Â s.srcÂ =Â "http://assets.pinterest.com/js/pinit.js"; 
Â Â Â Â Â Â Â Â varÂ xÂ =Â document.getElementsByTagName("script")[0]; 
Â Â Â Â Â Â Â Â x.parentNode.insertBefore(s,Â x); 
Â Â Â Â } 
Â Â Â Â ifÂ (window.attachEvent) 
Â Â Â Â Â Â Â Â window.attachEvent("onload",Â async_load); 
Â Â Â Â else 
Â Â Â Â Â Â Â Â window.addEventListener("load",Â async_load,Â false); 
})(); 
script>

Finally, I add the following code near the bottom of the news_article.html template for the "Chat" plugin from facebook

 <fb:commentsÂ ?Â numposts="15"Â <divÂ class="fb-comments"Â data-href="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>">fb:comments>