61
SMEDrieben
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/30 7:36

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


This is my global.php (language/nederlands/global.php)

define('_DATESTRING''j/n/Y G:i:s'); // kan naar eigen voorkeur aangepast worden
define('_MEDIUMDATESTRING''j/n/Y G:i'); // kan naar eigen voorkeur aangepast worden
define('_SHORTDATESTRING''d/m/Y'); // kan naar eigen voorkeur aangepast worden


and

define('_DBDATESTRING''Y-m-d');
define('_DBTIMESTRING''H:i:s');
define('_DBTIMESTAMPSTRING''Y-m-d H:i:s');


Is the _SHORTDATESTRING causing the problem ?

Thanks,

SMEDrieben



62
SMEDrieben
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/30 6:31

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


Perhaps I have a similar problem. If I add a new item in News, the published date is set to 1/1/1970. I entered 29/06/2014 in the New item page.

In the database, the date created is correct, but the publisehd date not (1/1/1970, in the database 64800.

How can I solve this ?

SMEDrieben



63
SMEDrieben
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/29 12:17

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


I think I found another bug: .tpl templates are not given in the templates admin page.

If you start in the configuration panel (mysite/admin.php), click the templates icon (mysite/modules/system/admin.php?fct=tplsets) and choose mytheme in the left panel, subdirectory modules/publisher, no templates are given.

If I go another module, in the same directory, e.g. news, all personalized templates are shown. The difference is the extension: .tpl in case of publisher, .html in case of news.

Is this a bug ?

SMEDrieben




64
SMEDrieben
Re: Publisher 1.02 Beta 3 for XOOPS 2.5.7 ready for testing
  • 2014/6/28 12:57

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


A few important steps further:

Those who want to recycle their personalized templates in the mytheme/modules/publisher folder must do 2 things:

- change the extension .html to .tpl in the names of the template files
- change the .html to .tpl in the templates themselves, e.g.

<{include file='db:publisher_header.html'}>


should be
<{include file='db:publisher_header.tpl'}>


The publisher pages are looking beatiful again !

My last question remains: what should I do with the .html templates attributed to Publisher in the _tpl tabe ?

SMEDrieben



65
SMEDrieben
Re: Publisher 1.02 Beta 3 for XOOPS 2.5.7 ready for testing
  • 2014/6/28 12:37

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


I've updated the Publisher and System modules several times, in different orders.

In the _tpl table, there are quite a lot of.tpl records attributed to the Publisher module. There are also 10 .html Publisher templates.

Should I remove the .html Publisher templates manually form the _tpl table ?

SMEDrieben



66
SMEDrieben
Re: Publisher 1.02 Beta 3 for XOOPS 2.5.7 ready for testing
  • 2014/6/27 18:48

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


Thanks for this version ! The tabs are back again in my system.

I have a strange experience with the templates. The look and feel of this module is quite different than before the upgrade. I tried to find out why, it looks severly mixed up.

I have templates in mytheme/modules/publisher folder. If I change something in these templates or in the .tpl that come with this version, nothing happens.

I changed the extension from .html to .tpl and emptied all caches. No change. General preferences: Check templates changes: is on yes.

Why don't changes in the templates in mytheme/modules/publisher or mydomain/modules/publisher/templates induce changes in how the data are presented ?

Thanks !

SMEDrieben



67
SMEDrieben
Re: extCal 2.37 Final is released: day names: solved
  • 2013/11/11 21:10

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


I still owe an answer to Mamba on the day names issues. In summary, day names in the calendar view were not in the desired language. The solution should be in language/nederlands/locale.php:

/* Set locale to Dutch */ 
setlocale(LC_ALL'nl_NL');


In modules/extcal/xoops_version.php the line:

setlocale(LC_TIME$xoopsConfig['language']);


must be commented out. Initially, it was terrible: the day names turned form english to danish and swedish ! Recently, my ISP moved my site to another server (and server location). Now it works as expected: Dutch day names.

Thanks and kind regards,

SMEDrieben



68
SMEDrieben
Re: Upgraded ExCal from 2.22 to 2.37 on XOOPS 2.5.6
  • 2013/8/10 20:47

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


I have experienced the same problem (absence of headers) after upgrading from 2.22 to 2.37. It is solved, but I don't know exactly what has solved. A few suggestions:
- cache as suggested by Mamba is important
- customized templates of 2.22 cannot be used in 2.37. Remove them from themes/yourtheme/modules/extcal; if you prefer customized templates, make new ones using the orignals in the 2.37 templates folder.
- start with new language files from the 2.37 download: don't use the 2.22 language files.

In my case, the headers returned.

SMEDrieben



69
SMEDrieben
Re: TDMStats 1.07 Ready for Testing on XOOPS 2.5.5
  • 2013/8/5 15:09

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


When can we expect a Final version of this module ? 1.08 Final ? This module has been for a long period of time RC.

SMEDrieben



70
SMEDrieben
Re: Publisher 1.0 Final: a few comments
  • 2013/8/4 15:34

  • SMEDrieben

  • Not too shy to talk

  • Posts: 173

  • Since: 2009/6/17


Dear Mamba,

I think Publisher is a fantastic module !

Users must realize that quite a lot of features can be modified by the (extensive) preferences menu. The permissions menu is important as well, since you have to arrange here what you wil see in some admin tabs.

I have some comments (in part already mentioned above):

- the category header field is a legacy (I think): it is only used in the WF-Sections display, as far as I could discover. In this field, you can insert xoops codes with a menu: however, xoops codes will not be recognized ! Wouldn't it be better to combine this field with the category description field ?
- the category description field: xoops codes used in this field are not recognized.
- category images cannot be selected from images already in the database or somewhere in de uploads folder. The module requires a copy of those images in its own folder in the uploads folder. I think it would be better if the module also could use images in others folder.
- the modules uses its own icons and not those in the Frameworks/modulesclasses/icons folder. For future releases it would be better to use the icons from Frameworks.


SMEDrieben




TopTop
« 1 ... 4 5 6 (7) 8 9 10 ... 17 »



Login

Who's Online

154 user(s) are online (115 user(s) are browsing Support Forums)


Members: 0


Guests: 154


more...

Donat-O-Meter

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

Latest GitHub Commits