eEmbed now included in XOOPS 2.6.0
Including and presenting Media has just become so much easier in the next version of XOOPS!
Richard just added the "oEmbed" capability to XOOPS 2.6.0
So what is oEmbed?
oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly, in other words, it allows embedding content from a website into another page.
An oEmbed exchange occurs between a consumer and a provider. A consumer wishes to show an embedded representation of a third-party resource on their own website, such as a photo or an embedded video. A provider implements the oEmbed API to allow consumers to fetch that representation.
In XOOPS, similar to 'Clickable' filter, Embed will process a URL alone on a line using the embed/embed package. For URLs supporting oEmbed, such as YouTube, the oembed result will be shown. For other URLs, a default media box, built from the page content, will be displayed. See example below of the code, and then representation provided thanks to oEmbed:
How cool is that?
You can test this version by forking or downloading it from our GitHub account
Comments?
Richard just added the "oEmbed" capability to XOOPS 2.6.0
So what is oEmbed?
oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly, in other words, it allows embedding content from a website into another page.
An oEmbed exchange occurs between a consumer and a provider. A consumer wishes to show an embedded representation of a third-party resource on their own website, such as a photo or an embedded video. A provider implements the oEmbed API to allow consumers to fetch that representation.
In XOOPS, similar to 'Clickable' filter, Embed will process a URL alone on a line using the embed/embed package. For URLs supporting oEmbed, such as YouTube, the oembed result will be shown. For other URLs, a default media box, built from the page content, will be displayed. See example below of the code, and then representation provided thanks to oEmbed:
How cool is that?
You can test this version by forking or downloading it from our GitHub account
Shortcodes are coming to XOOPS 2.6.0 :D
Richard continues to doing amazing changes to XOOPS 2.6.0. The latest addition are "Shortcodes", which are probably best known from WordPress. I was actually hoping for it for a long, long time, and I was very happy to see that Richard has added it to XOOPS! YES!!!
It was possible thanks to refactoring of our old TextSanitizer. You can read more details from Richard's info on GitHub
Quote:
What does it mean for XOOPS developers? We'll be able now to simplify a lot of activities around designing the best looking Websites for our users and customers!
Also our users will be able to add tons of cool features without any programming!
For those of you who never worked with ShortCodes, let's provide a short overview and a little tutorial. The basic classes that we'll be using, are the TextSanitizer classes refactored by Richard:
Currently we have following classes derived from FilterAbstract :
- Censor
- Clickable
- Quote
- SyntaxHighlight
- TextFilter
- Xss
and following classes derived from ExtensionAbstract:
- Flash
- Iframe
- Image
- Mms
- Mp3
- Rtsp
- SoundCloud
- UnorderedList
- Wiki
- Wmp
- XoopsCode
- YouTube
For our purposes we'll be using mainly the ExtensionAbstract class. Let's see now how can we use it to create ShortCodes for Google Charts and Google Maps (Read more-->)
Read more... | 24277 bytes more | 6 comments
It was possible thanks to refactoring of our old TextSanitizer. You can read more details from Richard's info on GitHub
Quote:
MyTextSanitizer has become Xoops\Core\Text\Sanitizer.
Highlights:
- Single unified configuration filexoops_data/configs/system_sanitizer_prefs.yml
- Extensions (i.e. YouTube) are now a SanitizerComponent, a base class that also includes Filters (i.e. Xss)
- Each SanitizerComponent auto-configures, and configuration is automatically updated with new additions
- Custom components can be added via response to core.sanitizer.configuration.defaults event
- ShortCodes (WordPress style) are now the basis of XoopsCode and extensions
- Custom ShortCodes can be added via response toevent, or by directly accessing the ShortCodes engine withcore.sanitizer.shortcodes.addSanitizer::getShortCodes()
- All built-in components and shortcodes can be overridden with same named custom replacements
- Some extensions have updated syntax. For example:[youtube=640,385]https://www.youtube.com/watch?v=JxS5E-kZc2s[/youtube]
can now be:[youtube url="JxS5E-kZc2s" width="640" height="385" /]
(It also can use virtually any known YouTube URL as the url attribute.)
- Another example is SoundCloud, which now can directly support the "Wordpress code" option offered in the Share/Embed dialog on soundcloud.com.
The old styles are still accepted for compatibility with existing content, and not all extensions have conversions to new styles, yet. There is more work to be done, but the backing code is now in place.
What does it mean for XOOPS developers? We'll be able now to simplify a lot of activities around designing the best looking Websites for our users and customers!
Also our users will be able to add tons of cool features without any programming!
For those of you who never worked with ShortCodes, let's provide a short overview and a little tutorial. The basic classes that we'll be using, are the TextSanitizer classes refactored by Richard:
Currently we have following classes derived from FilterAbstract :
- Censor
- Clickable
- Quote
- SyntaxHighlight
- TextFilter
- Xss
and following classes derived from ExtensionAbstract:
- Flash
- Iframe
- Image
- Mms
- Mp3
- Rtsp
- SoundCloud
- UnorderedList
- Wiki
- Wmp
- XoopsCode
- YouTube
For our purposes we'll be using mainly the ExtensionAbstract class. Let's see now how can we use it to create ShortCodes for Google Charts and Google Maps (Read more-->)
Translation Project for final Packaging of Signed 2.2.x Final Release
Signed 2.2RC Module - Translation Project
This module is to be translated in the supporting groups for final candidate packaging for the XOOPS SVN, once you have done the translation the translated signature files as well as the language files have to be package and sent to simon@staff.labs.coop with any comments or changes that needed to happen outside any core language folded file-base.
You can connect to the Author of the module with Skype on the account: antony.cipher – this is if you have any question or comments for the module! But please read the PDF before you do contact incase it answers any questions
Please notify either by email and wait for confirmation as a translator, as you will eventually once final packaging being done noted in the code stamp as one of the authors; which you can also do in the resource files.
Module Download: ~~~::[ *.7z ! *.rar ! *.tar.gz ! *.tar.bz2 ! *.zip ! *.tar ! *.bz2 ! *.rar5 ! *.jar ]::~~~
XOOPS SVN: https://sourceforge.net/p/xoops/svn/HEAD/tree/XoopsModules/signed/
Download Project PDF (English) -- Signed 2.2.1 Final Release - Translation Project.pdf
Folder's for Translation
Quote:
xoops2.5_signed_2.2RC.tar.gz
+ modules / signed / language / english (translate folder)
+ xoops_lib / modules / signed / processes / english (translate folder)
XOOPS 2.6.0 Goes PSR-4 plus Other Core Enhancements
1) Richard is powering forward with some very cool enhancements for the Core of XOOPS 2.6.0. Recently he committed these enhancements: Quote: He also posted a RFC (Request for Comments) on three issues: - Namespaces - Moduels vs. Extensions - Add a modinfo column to system_module Quote: Please respond directly on GitHub 
It is also worth to mention that Eduardo is making some major progress on creating a new "Presentation Layer" in XOOPS 2.6.0 based on his excellent "Common Utilities" Slowly but surely, the pieces of the puzzle called XOOPS 2.6.0 are starting to fall in place!
Read more... | 1 comment
First stage of localization refresh #261, and other misc cleanup - Implements localized date and time handling. PHP DateTime objects used extensively in all date processing. Localization is provided by [Punic](https://github.com/punic/punic) - Add `Request::getDateTime()` Returns a `\DateTime` object from `Form\DateSelect` and `Form\DateTime` input. The form classes can also receive DateTime objects as values. Form dates are now local to the user, or system default if no user. - Timezones are now PHP `DateTimeZone` names, not float offsets. PHP DateTime and DateTimeZone objects are used to implement all calculations. This makes handling of things like daylight savings or summer time automatic. - Add `Dtype::TYPE_TIMEZONE` to store and restore \DateTimeZone objects - Add Smarty `datetime` modifier, allowing both unix timestamps and DateTime objects to be processed by XoopsLocale::formatTimestamp(), allowing date and time formatting to be controlled in the presentation layer with tags like `<{$datevariable|datetime:'short'}>` - XoopsList class broken into individual classes in `Core\Lists`. These class are expected to implement `Core\Lists\AbstractList`. These can interact directly with form fields, reducing code complexity and duplication. - Add select_editor 'formtype' for $modversion['config']. This removes the need for active code to load editors in a module's xoops_version.php. All editor lists now originate from one point, Core\Lists\Editor - New subclass of Form\Element, OptionsElement which provides the standard option methods. List classes can interact with any extender of OptionsElement, see Core\Lists\AbstractList::setOptionsArray() - `Xoops_*` classes moved to actual `Xoops` namespace. These *PSR-0*, pseudo namespaces are obsolete. Their removal allows us to move to PSR-4 based loading for the Xoops namespace. - CountryFlag service no longer delivers bare URL to resource, only HTML to display flag. This allows more flexibility on how the flag is presented. - Accept `Trowable` in `Core\Logger::handleExeception()` (PHP7)
I've given a lot of consideration to modules, and have a few ideas I want to present. If you have comments, alternatives, objections or other feedback, please respond. Baring objections, I would like to move on this quickly. Namespaces Add a namespace column to system_module table. This would be the PHP namespace for the module's code. It would map to the module's class directory in PSR-4 fashion. This would be implemented automatically for all active modules with a namespace specified. Note, this will be separate from the composer maintained loader, since composer has no way of knowing if a module is "active" in XOOPS. Autoloading components from modules which are not installed or inactive could create lots of issues. With the namespace enabled, most of the old directory positional naming constructs can be replaced with objects. For example, instead of using the $modversion['onInstall'] entry to locate a file to include, then building function names based on the module name, the code would look more like this:Our current preloads directory, with possibly multiple files, would disappear, and everything would reside in the$moduleNamespace . 'System\Events' class instead. In this scheme, the class/System directory would be reserved for the system specified classes. Each would have a specific interface defined. There are more details, but this should illustrate the concept. Modules vs. Extensions Based on some thoughts from @bitcero and some more consideration, I propose eliminating the extension concept as is, and moving to a module category system to make management cleaner. Categories would be something like this: Category: Usage ------------------------- Content: articles, blogs, calendars, forums, etc. Developer: module builders, schema tools Extension: service providers, system enhancement Locale: i18n resources, language packs Theme: for the new module based themes This is not carved in stone, but the idea is to create a limited, high level taxonomy to categorize modules. The defined categories would be enforced, as we don't need a free for all. The module listing functions would be adapted to deliver lists of individual categories. A category column on the system_module table would hold this item. To support subtle differences, each category would be backed by a sub class of the system module class, but all would offer the same functionalities. Add a modinfo column to system_module Caching of the $modversion array has been suggested many times. Adding a single column set on install and update can accomplish this, and the existing getInfo() and related methods will be able to use the column data as the source, eliminating the need to hit the filesystem. With this information in the database, all the module object access can be fully cached, which should speed thing up a bit.if (class_exists($moduleNamespace . 'SystemInstall')) {
$install = new $moduleNamespace . 'SystemInstall;
$success = $install->postInstall($module);
}
It is also worth to mention that Eduardo is making some major progress on creating a new "Presentation Layer" in XOOPS 2.6.0 based on his excellent "Common Utilities" Slowly but surely, the pieces of the puzzle called XOOPS 2.6.0 are starting to fall in place!
6 Modules for XOOPS 2.6.0 added to GitHub (Alpha version)
Laurent JEN (aka DuGris) has developed couple of years ago six very nice modules for XOOPS 2.6.0
I've started updating them to reflect the changes done to XOOPS 2.6.0 Core since then, and they are now on GitHub in the XOOPS 2.6.0+ Modules section.
Clearly, the update is still work in progress and some of the modules don't work yet properly due to the changes in Core, but hopefully soon they will become more stable. Of course, as always, you can fork them and help us with the development!
Demo DuGris' Demo Website:
Download/Fork: XOOPS 2.6.0+ Modules on GitHub:
XooContact
XooGhost
XooPartners
XooSitemap
XooSocialnetwork
XooTags
XOOPS 2.6.0
Please note that the next version of XOOPS is being actively developed on GitHub, and you're encouraged to fork it, test it, and contribute back!
Read more... | 9 comments
I've started updating them to reflect the changes done to XOOPS 2.6.0 Core since then, and they are now on GitHub in the XOOPS 2.6.0+ Modules section.
Clearly, the update is still work in progress and some of the modules don't work yet properly due to the changes in Core, but hopefully soon they will become more stable. Of course, as always, you can fork them and help us with the development!
Demo DuGris' Demo Website:
Download/Fork: XOOPS 2.6.0+ Modules on GitHub:
XooContact
XooGhost
XooPartners
XooSitemap
XooSocialnetwork
XooTags
XOOPS 2.6.0
Please note that the next version of XOOPS is being actively developed on GitHub, and you're encouraged to fork it, test it, and contribute back!
New Contact Module
Hi all,
The German XOOPS Team released today a new/updated Contact module.
This module uses Bootstrap templates which makes it perfect for modern responsive websites.
Features:
- xBootstrap Templates
- Google Recaptcha (optional)
- easily included Google Maps
Please test the module and give us feedback so we can improve it.
Demo:
You can see a demo of this module here:
http://shield.xoopsthemes.com/modules/contact/
Download:
The module can be downloaded and forked here:
https://github.com/myxoops/contact
Thanks
Read more... | 20 comments
The German XOOPS Team released today a new/updated Contact module.
This module uses Bootstrap templates which makes it perfect for modern responsive websites.
Features:
- xBootstrap Templates
- Google Recaptcha (optional)
- easily included Google Maps
Please test the module and give us feedback so we can improve it.
Demo:
You can see a demo of this module here:
http://shield.xoopsthemes.com/modules/contact/
Download:
The module can be downloaded and forked here:
https://github.com/myxoops/contact
Thanks
New Tutorials added to XOOPS Documentation
Last year we've started to standardize on GitBook as our delivery mechanism for XOOPS Documentation (see here)
Today I've added couple of new Tutorials: xLanguage and NewBB. They are not yet finalized and are still "work in progress", but because of this it gives the XOOPS Community the opportunity to get involved and help with improving our documentation, which we know is badly needed!
Please note that ALL of the XOOPS books are hosted on GitHub in the XOOPS Documentation repository, and therefore they all can be "forked", improved by you, and your modifications can be then submitted back to the original for inclusion. This is exactly the same process as with using GitHub as a Version Control for source code
The beauty of it is that you can learn and practice how to use GitHub, and at the same time help XOOPS to improve its documentation, especially since for writing documentation there is no programming expertise needed, but only the familiarity with the module. You can also start using the particular module and write the documentation as you learn how to use it.
The advantage of this approach is very clear: the XOOPS developers have limited amount of time, and they can:
1) spend it on debugging and improving existing modules, and developing new ones,
2) or they can spend it on writing tutorials.
It would be truly fantastic if those XOOPS users who don't have programming skills, could help us with documentation!
Read more... | 3 comments
Today I've added couple of new Tutorials: xLanguage and NewBB. They are not yet finalized and are still "work in progress", but because of this it gives the XOOPS Community the opportunity to get involved and help with improving our documentation, which we know is badly needed!
Please note that ALL of the XOOPS books are hosted on GitHub in the XOOPS Documentation repository, and therefore they all can be "forked", improved by you, and your modifications can be then submitted back to the original for inclusion. This is exactly the same process as with using GitHub as a Version Control for source code
The beauty of it is that you can learn and practice how to use GitHub, and at the same time help XOOPS to improve its documentation, especially since for writing documentation there is no programming expertise needed, but only the familiarity with the module. You can also start using the particular module and write the documentation as you learn how to use it.
The advantage of this approach is very clear: the XOOPS developers have limited amount of time, and they can:
1) spend it on debugging and improving existing modules, and developing new ones,
2) or they can spend it on writing tutorials.
It would be truly fantastic if those XOOPS users who don't have programming skills, could help us with documentation!
Premium Themes - 16 XOOPS Themes Free!
I bring you 16 premium themes developed by me. Soon i will be releasing new themes free and premium, based on xBootstrap. I hope you enjoy.
News (in portuguese): http://xoopsfire.com/modules/publisher/item.php?itemid=53
Download: http://xoopsfire.com/modules/TDMDownloads/viewcat.php?cid=22
Demos: http://demo.xoopsfire.com/
Read more... | 9 comments
News (in portuguese): http://xoopsfire.com/modules/publisher/item.php?itemid=53
Download: http://xoopsfire.com/modules/TDMDownloads/viewcat.php?cid=22
Demos: http://demo.xoopsfire.com/
Xoops Blog Theme (For Publisher)
Xoops Blog theme, for publisher.
Demo :
http://xoopstasarim.com
Download :
https://github.com/XoopsThemes/blog/releases
Read more... | 738 bytes more | 5 comments
Demo :
http://xoopstasarim.com
Download :
https://github.com/XoopsThemes/blog/releases
UHQ GeoLocate v0.96 released!
It's been another couple of years since the module has been updated. There are a few tweaks in here that now set the minimum version to XOOPS 2.5.7.
Functionally, this should be ready for a production implementation. There are some more administrative pieces I've got in my to-do list before I give it the big 1.0.
Direct downloads are here.
Also, this project can be found on GitHub here.
From the changelog:
====[ 0.96 -- 2015-06-16 ]====
Code Changes
* Modified directory structure to really fit in GitHub. (Mamba)
* IPInfoDB v2 APIs are depreciated and have been removed as options. Update scripts will change this accordingly.
* Help section utilizes new help structure for 2.5.7+
* Update script uses language localization in admin.php,
* Update script now produces verbose notes for updates to v0.96.
Fixes
* Removed redundant file check in update script.
Notes
* Dev environment is now XOOPS 2.5.7.1
====[ 0.95 -- Not Released ]====
Fixes
* Fixed a couple rendering issues which would see an error condition.
* Sub-branch adjusting to quirks in XOOPS 2.6.0 Alpha 2.
Login
Search
Recent Comments
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
Latest GitHub Commits
Archives
News archives
- January 2017
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- July 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
- March 2003
- February 2003
- January 2003
- December 2002
- November 2002
- October 2002
- September 2002
- August 2002
- July 2002
- June 2002
- May 2002
- April 2002
- March 2002
- February 2002
- January 2002
- December 2001
- December 1969