Support Forums - All Posts - XOOPS Web Application System

21

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/17 23:30
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Quote:

Mamba wrote:
the fmContent module was different, because it kept all the "cloned" modules' data in the same table.[...]

The Publisher's way is better, in my view, because it creates "independent" clones that are easily transferable to other XOOPS installations.

I think so too.
It seems to me that this is a good time for Trabis and Voltan cooperation. Why?

1. Both modules are designed to the same: they are an advanced information management system, both static and dynamic.
2. a) FMContent, that's much more than a module for static content.
b) It has quite good, working util for articles sort order management, well-resolved image display. But cloning method and SEO are "under constraction" (from the other side, SEO is designed holistically).
3. Publisher is totally clonnable. It's still RC (I suppose, the signature of Trabis is to have all modules still "under construction"

), but it works and has some interesting solutions (author's mask, etc.). But there are no good tools for sorting the items, partially SEO and a lot of errors (image management, sth in some blocks, complicated configuration).

If Voltan and Trabis began to collaborate, XOOPS quickly should have a great and flexible module for content management, both static and dynamic. After adding the import tool from Smartsections, niusów, MastopPublish and Content it would be great.

Quote:

irmtfan wrote:
I still think the GIjo way of cloning modules is better (maybe the best way). In the cube they called it "Duplicatable V3 (D3)"

A part of module functions can be placed in XOOPS_LIB - it can be common for all instances/clones.

I still beleve, it will be possible for me to test last RC version of very good "content module" before my summer trip on the sea. It will start about 9th of June - next time I should have a time to test anythig after 25 of July.

22

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/16 20:13
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Correct - that's right.

In a short time I'm going to create two copies of publisher (publisher and "new publisher" in my website wodniacy.eu - the first one just is installed and now we try to create a content (it's some kind of almanach/vademecum for leaders of seascouts), the second one it will be vademecum for sailors, about sailing. Two different modules with the same functionallity.

I suppese, your method of importing datas was possible in fmcontent, because version 1.5 and 1.1 was based on one pocked of tables both for oryginal and clones.

23

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/16 19:17
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Mamba, I don't think so - clone uses different tables, than publisher - check sql files in both of them (prefixes for tables in files).

It means, publisher is fully clonable.

24

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/16 12:54
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Quote:

irmtfan wrote:
I test the publisher and its cloning is good.
but i still dont know how to import the old "smartcontent" by keeping the directory name.
I installed "publisher" and then i import the old smartcontent successfully.
then how i can change the "publisher" to "smartcontent"?
same question will be raised for any other module that uses this way of cloning.
I mean if Voltan follow this way of cloning and write an import script then how i can upgrade my old "smartcontent" by keeping the directory name?

I can only imagine two ways:

1. a) Import from smatrfactory to publisher
b) deinstalation sf module
c) creating a clone of publisher called smartfactory
d) import from publisher to new smartfactory (if it's possible)

2. a) Import from smatrfactory to publisher
b) deinstalation sf module
c) creating a clone of publisher called smartfactory
d) in phpmyadmin export publisher tables with data to a file
e) in eg. notepad++ edition that file to change table-prefix from "publisher" to "sf clone"
f) import data from a file to empty "sf clone" tables

In the past I tryed to place news datas from MDPro to XOOPS by using a second method and it was done successfully.

25

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/16 9:21
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Quote:

irmtfan wrote:
...you just need to copy 'News" to your "modules" directory. then you can rename "News" to your favorite (eg: YOUCLONE) and install it like any other module. So you have these folders in the modules directory:
/modules/news
/modules/YOURCLONE
[...]
The problem is exactly here. you can not have the "Old news" in your website because as you already well mentioned, Voltan hardcoded the "news" directory and now it has been reserved for all clones created from his news module

That's right. So, I think, in this moment it will be good to make Voltan's module clonable in the same way Trabis use in Publisher.

Future request:
1. It wiil be good to have a possibility to define articles sort order not only for module, but for any topic too. This sould make a module more flexible => in one component there will be a place for topics with static structure of content (eg. informations about... sport team) and others, working like news (eg. sorting by date).
2. For the index site of module it will be good to add a possibility to select current topics (eg. only topics working like a news) to create a list with articles - I'm not sure, but one of joomla components should have such functionality.

26

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/15 15:13
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Two things:

1. irmtfan - I suppose, you dotn't understand my last post.

I tested two versions of Voltan's module:

a) first called "news", which is installed on my XOOPS site, where I do not have the original old "news" ver. 1.66 installed - it allowed me to see most of the module functions... and problems,
b) second one, being a clone of the first (it was named: "fmcontent"). This clone was prepared in first website and copied and installed in another XOOPS site, in which I have the original old "news" module, but there isn't Voltan's "news" module installed.

2. This is a good time to do one thing.
Voltan could try to clone his module with a generic name (testnews, fmcontent2 or testcontent) and install it in an empty, test XOOPS site. In this way, he will be able to detect all wrong parts of the code (hardcoded too) and make the "clone" such functional as his "news".
This would enable to create this module really clonable and to increase a group of testers. And also allow posting changes tohttp://xoops.svn.sourceforge.net/ not only in branches/news, but in branches/"clone-testversion" - having standalone "clone" will be good for testers with only one webside and old "news" module installed.

wodniacy.eu | pzj.pl

27

Re: TDMStats 1.07 Ready for Testing on XOOPS 2.5.5

2012/5/14 19:45
panwac
Just popping in
Posts: 62
Since: 2005/11/12

In funcion_xoStats.php file a part of code:


istat.src = "'.XOOPS_URL.'/modules/TDMStats/counter.php?sw="+screen.width+"&sc="+screen.colorDepth+"&page="+location.href+"&ismodule='.$ismodule.'";

should be changed to:


istat.src = "'.XOOPS_URL.'/modules/TDMStats/counter.php?sw="+screen.width+"&amp;sc="+screen.colorDepth+"&amp;page="+location.href+"&amp;ismodule='.$ismodule.'";

28

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/13 15:00
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Next informations:

1. When I created a clone of module and tryed to install it on the other site, I found an error in header.php. I changed 3 lines of code and after that clone start work.

In lines 28-31:


require_once XOOPS_ROOT_PATH . '/modules/news/include/functions.php';

include_once XOOPS_ROOT_PATH . '/modules/news/class/perm.php';

require_once XOOPS_ROOT_PATH . '/modules/news/class/utils.php';

were replaced with:


require_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . 'include/functions.php'; 

include_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . 'class/perm.php'; 

require_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . 'class/utils.php';

2. The same problem is in file /admin/header.php. When you are going to your clone admin site in CP, you've got a message:
Quote:

Fatal error: require_once(): Failed opening required '/home/.../sitename/modules/news/class/folder.php' (include_path='.:/opt/php-5.3/lib/php') in /home/.../sitename/modules/clonename/admin/header.php on line 27

I replaced lines 27-29:


require_once XOOPS_ROOT_PATH . '/modules/news/class/folder.php'; 

require_once XOOPS_ROOT_PATH . '/modules/news/include/functions.php'; 

require_once XOOPS_ROOT_PATH . '/modules/news/class/utils.php';

with


require_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . '../class/folder.php'; 

require_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . '../include/functions.php'; 

require_once dirname( __FILE__ )  . DIRECTORY_SEPARATOR . '../class/utils.php';

3. There is sth wrong with link to pdf site of article.

4. Links in relative articles table (on article site) are not correct - topic name in links is... strange (random?).

5. I spent a few hours to start SEO, but whithout success - the only link working good was to topic side (after small changes in .htaccess file).

Sorry for my bad english. ;)

Edit: THIS MODULE IS NOT CLONABLE!
To make it work without a clone called "news" in the same xoops instalation... propabbly I should change codes in all files. :/

29

Re: Fmcontent module 1.1 in xoops 2.5.4

2012/5/11 21:21
panwac
Just popping in
Posts: 62
Since: 2005/11/12

O.K. - Today I have checked fmcontent module (version news from sf). First view:

1. When a clone (called fmcontent) was created, inside the lang files no changes were prepared - any defines still have prefix from news (_NEWS_AM_GLOBAL_ADD_CONTENT etc.).
2. During testing a module (version "news"), in CP I haven't possibility to change order of articles - drag and drop methode don't work. It means, sorting by order is dead.
3. there is sth wrong with block 'Article page" - I've got white page, when I'm trying edit it or, (on user side), when it's active.
-------
xoops 2.5.4
php 5.3.10
tested in FF 12

Edit: I found a reason for point no 2. It works, when sort order for user area and admin articles page is set on order.

Next error. When a number of digits for ID isn't "1" (eg.: "3"), then for any topic I've got a message "Topic not exist".

wodniacy.eu | pzj.pl

30

Re: Fmcontent new version : Test and report bugs

2012/4/15 21:10
panwac
Just popping in
Posts: 62
Since: 2005/11/12

Quote:

And one can help me in codeing? or make all needed options? and test?

I'm not sure you are asking about FMContent or "newNews" version and I'm not a coder, but... I can try to test a module in free time. Everything, to have final, stable version of content module for Xoops 2.5.x ;)

Stats
Goal:	$100.00
Due Date:	Apr 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: TDMStats 1.07 Ready for Testing on XOOPS 2.5.5

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent module 1.1 in xoops 2.5.4

Re: Fmcontent new version : Test and report bugs

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}