Support Forums - All Posts - XOOPS Web Application System

5651

Re: TDMCreate 1.91 alpha 1 for Testing

2015/6/29 23:19
Mamba
Moderator
Posts: 11373
Since: 2004/4/23

Quote:

I've released a patch

Thanks, Timgno! This time I was able to install it without any problems.

So far, I see two problems:

1) In /admin/modules.php you need to change from:

$GLOBALS['xoopsTpl']->assign('modPathIcon16', $modPathIcon16);

to:

$GLOBALS['xoopsTpl']->assign('modPathIcon16', TDMC_URL.'/'.$modPathIcon16);

otherwise the images are not visible, since XOOPS is looking for them in /admin/icons/16

2) You still didn't fix the issue with with the case when we don't assign any name to a table prefix. Since it is "optional", I don't assign anything, and for several months now I am getting this error:

 Parse error: syntax error, unexpected ')', expecting variable (T_VARIABLE) or '$' in C:/wamp64/www/257tdmc191/modules/zumba3/index.php on line 34

with the code being:

 if ($categoriesCount > 0) { 
    $categoriesAll = $categoriesHandler->getAllCategories(); 
    include_once XOOPS_ROOT_PATH . '/class/tree.php'; 
    $mytree = new XoopsObjectTree($categoriesAll, 'id', 'parent'); 
    foreach (array_keys($categoriesAll) as $)

It seems like you want to assign the prefix to the variable, but if it's not there, you're getting only the "$" sign:

Quote:

foreach (array_keys($categoriesAll) as $)

So please add to your test cases a scenario where the user doesn't choose to add a prefix for the table...

But overall it is looking better! Congratulations!

And thank you for keeping working on this!

Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

5652

@required::- Complete support of xoops_version.php module info in about dialogue!

2015/6/29 21:19
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

While putting together the planning set for please I went back through all the modules on the shelf to see what where the commonality headers and array elements that needed to be supported in the help "about module" system menu which is way limited at the moment.

If you turn your attention to: https://sourceforge.net/p/xoops/svn/HEAD/tree/XoopsModules/please/trunk/xoops_version.php ~~ you will find the following need to be included and formatted into the dialogue system menu..

 $modversion['dirname']                     = _MI_PLEASE_MODULE_DIRNAME; 
$modversion['name']                     = _MI_PLEASE_MODULE_NAME; 
$modversion['version']                     = _MI_PLEASE_MODULE_VERSION; 
$modversion['releasedate']                 = _MI_PLEASE_MODULE_RELEASEDATE; 
$modversion['status']                      = _MI_PLEASE_MODULE_STATUS; 
$modversion['description']                 = _MI_PLEASE_MODULE_DESCRIPTION; 
$modversion['credits']                     = _MI_PLEASE_MODULE_CREDITS; 
$modversion['author']                      = _MI_PLEASE_MODULE_AUTHORALIAS; 
$modversion['help']                        = _MI_PLEASE_MODULE_HELP; 
$modversion['license']                     = _MI_PLEASE_MODULE_LICENCE; 
$modversion['official']                    = _MI_PLEASE_MODULE_OFFICAL; 
$modversion['image']                       = _MI_PLEASE_MODULE_ICON; 
$modversion['module_status']             = _MI_PLEASE_MODULE_STATUS; 
$modversion['website']                     = _MI_PLEASE_MODULE_WEBSITE; 
$modversion['dirmoduleadmin']             = _MI_PLEASE_MODULE_ADMINMODDIR; 
$modversion['icons16']                     = _MI_PLEASE_MODULE_ADMINICON16; 
$modversion['icons32']                     = _MI_PLEASE_MODULE_ADMINICON32; 
$modversion['release_info']             = _MI_PLEASE_MODULE_RELEASEINFO; 
$modversion['release_file']             = _MI_PLEASE_MODULE_RELEASEFILE; 
$modversion['release_date']             = _MI_PLEASE_MODULE_RELEASEDATE; 
$modversion['author_realname']             = _MI_PLEASE_MODULE_AUTHORREALNAME; 
$modversion['author_website_url']         = _MI_PLEASE_MODULE_AUTHORWEBSITE; 
$modversion['author_website_name']         = _MI_PLEASE_MODULE_AUTHORSITENAME; 
$modversion['author_email']             = _MI_PLEASE_MODULE_AUTHOREMAIL; 
$modversion['author_word']                 = _MI_PLEASE_MODULE_AUTHORWORD; 
$modversion['status_version']             = _MI_PLEASE_MODULE_VERSION; 
$modversion['warning']                     = _MI_PLEASE_MODULE_WARNINGS; 
$modversion['demo_site_url']             = _MI_PLEASE_MODULE_DEMO_SITEURL; 
$modversion['demo_site_name']             = _MI_PLEASE_MODULE_DEMO_SITENAME; 
$modversion['support_site_url']         = _MI_PLEASE_MODULE_SUPPORT_SITEURL; 
$modversion['support_site_name']         = _MI_PLEASE_MODULE_SUPPORT_SITENAME; 
$modversion['submit_feature']             = _MI_PLEASE_MODULE_SUPPORT_FEATUREREQUEST; 
$modversion['submit_bug']                 = _MI_PLEASE_MODULE_SUPPORT_BUGREPORTING; 
$modversion['people']['developers']     = explode("|", _MI_PLEASE_MODULE_DEVELOPERS); 
$modversion['people']['testers']        = explode("|", _MI_PLEASE_MODULE_TESTERS); 
$modversion['people']['translaters']    = explode("|", _MI_PLEASE_MODULE_TRANSLATERS); 
$modversion['people']['documenters']    = explode("|", _MI_PLEASE_MODULE_DOCUMENTERS); 
 
// Requirements 
$modversion['min_php']                    = '5.3.7'; 
$modversion['min_xoops']                  = '2.5.7'; 
$modversion['min_db']                     = array('mysql' => '5.0.7', 'mysqli' => '5.0.7'); 
$modversion['min_admin']                  = '1.1';

*geekwrite == you know that should be geekscribe -- you scribe code not write, anyway in XOOPS and ++sf you can have in the bridge between alpha too beta a total of ten releases like for example 7 alpha and 3 beta or 6 alpha and four beta's and so on, we are in no hurry i suggest you put these in so I can not have to in 2.7 -- offering future versioning write-back!

btw... there is over 5000 documenting errors for the industry standard phpDocumentor -- when your done in the alpha let me know and add me to the git and I will with you go through and fix them all so there 0 errors in the function documentations -- they need to be extensive!!

5653

Suggest DVD/CD Database

2015/6/29 18:47
dyraven
Just popping in
Posts: 15
Since: 2009/10/7

Can anyone suggest a module for creating a searchable DVD movie/CD music database? I am still using Xoops2.4.5.

The idea is to have my DVD's cataloged on my site so that I can access them via wi-fi on my Ipad. Any ideas?

5654

Xoops Module ~ Please ~ Email Ticket's with Keyword(s) Grouping Supportives

2015/6/29 18:18
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

Hi how are you all? I thought I would talk about the new module I am working on called: please (SVN). It is going to be an email ticketer a bit like Request Tracker but supporting attachments as well as HTML content etc.

It going to work by polling via eith a class lib or extensions, IMAP or POP3, as well as having other options I am yet to decide if they will be in the first version..

It is also going to have support for MantisBT.org so your departmental staff can raise to a support level two through mantis off the XOOPS portal..

The database concept looks like:-

 CREATE TABLE `please_addresses` ( 
  `id` int(14) NOT NULL, 
  `address` varchar(198) DEFAULT '', 
  `uid` int(11) DEFAULT '0', 
  `recieved` int(12) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `tickets` int(12) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  `action` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`address`(18),`uid`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_bcc` ( 
  `id` mediumint(30) NOT NULL, 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `address-id` int(14) DEFAULT '0', 
  `name-id` int(14) DEFAULT '0', 
  `email-id` mediumint(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`address-id`,`name-id`,`email-id`,`ticket-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_cc` ( 
  `id` mediumint(30) NOT NULL, 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `address-id` int(14) DEFAULT '0', 
  `name-id` int(14) DEFAULT '0', 
  `email-id` mediumint(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`address-id`,`name-id`,`email-id`,`ticket-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_contents` ( 
  `id` mediumint(30) NOT NULL, 
  `key` varchar(44) DEFAULT '', 
  `text` longtext, 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`key`(20)) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences` ( 
  `id` mediumint(38) NOT NULL, 
  `method` enum('email','pm','staff','mantis','unknown') DEFAULT 'unknown', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `department-id` mediumint(6) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences_bcc` ( 
  `id` mediumint(38) NOT NULL, 
  `bcc-id` mediumint(30) DEFAULT '0', 
  `department-id` mediumint(6) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `viewed` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences_cc` ( 
  `id` mediumint(38) NOT NULL, 
  `cc-id` mediumint(30) DEFAULT '0', 
  `department-id` mediumint(6) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `viewed` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences_contents` ( 
  `id` mediumint(38) NOT NULL, 
  `correspondence-id` mediumint(38) DEFAULT '0', 
  `ticket-contents-id` mediumint(30) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences_relayed` ( 
  `id` mediumint(38) NOT NULL, 
  `relayed-id` mediumint(30) DEFAULT '0', 
  `department-id` mediumint(6) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `viewed` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_correspondences_to` ( 
  `id` mediumint(38) NOT NULL, 
  `to-id` mediumint(30) DEFAULT '0', 
  `department-id` mediumint(6) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` mediumint(18) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `viewed` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments` ( 
  `id` int(6) NOT NULL, 
  `code` varchar(3) DEFAULT 'ABC', 
  `name` varchar(128) DEFAULT '', 
  `description` tinytext, 
  `mantis-username` varchar(45) DEFAULT '', 
  `mantis-password` varchar(198) DEFAULT '', 
  `mantis-project-id` int(11) DEFAULT '0', 
  `manager-uid` int(11) DEFAULT '0', 
  `manager-bcc` enum('all-email','closed-email','all-pm','closed-pm','none') DEFAULT 'none', 
  `manager-mantis-username` varchar(45) DEFAULT '', 
  `manager-mantis-password` varchar(198) DEFAULT '', 
  `mantis` enum('yes','no') DEFAULT 'no', 
  `gid` int(8) DEFAULT '0', 
  `tickets` int(12) DEFAULT '0', 
  `staff` int(12) DEFAULT '0', 
  `clients` int(12) DEFAULT '0', 
  `raised` int(12) DEFAULT '0', 
  `latest-id` mediumint(30) DEFAULT '0', 
  `closed-id` mediumint(30) DEFAULT '0', 
  `signature` varchar(300) DEFAULT '', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments_keywords` ( 
  `id` int(18) NOT NULL, 
  `department-id` int(6) DEFAULT '0', 
  `keyword-id` int(20) NOT NULL, 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`keyword-id`,`department-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments_mantis_projects` ( 
  `id` int(6) NOT NULL, 
  `project-id` int(12) DEFAULT '0', 
  `project-name` varchar(128) DEFAULT '', 
  `project-description` tinytext, 
  `tickets` int(12) DEFAULT '0', 
  `clients` int(12) DEFAULT '0', 
  `raised` int(12) DEFAULT '0', 
  `latest-mantis-id` mediumint(30) DEFAULT '0', 
  `closed-mantis-id` mediumint(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments_staff` ( 
  `id` int(18) NOT NULL, 
  `department-id` int(6) DEFAULT '0', 
  `state` enum('active','inactive','holidays') DEFAULT 'active', 
  `messaging` enum('email','pm','none') DEFAULT 'email', 
  `uid` int(12) DEFAULT '0', 
  `open` int(12) DEFAULT '0', 
  `tickets` int(12) DEFAULT '0', 
  `closed` int(12) DEFAULT '0', 
  `clients` int(12) DEFAULT '0', 
  `raised` int(12) DEFAULT '0', 
  `votes` int(12) DEFAULT '0', 
  `rating` int(12) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  `mantis-username` varchar(45) DEFAULT '', 
  `mantis-password` varchar(198) DEFAULT '', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`department-id`,`state`,`uid`,`open`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments_staff_keywords` ( 
  `id` int(18) NOT NULL, 
  `department-id` int(6) DEFAULT '0', 
  `staff-id` int(18) NOT NULL, 
  `keyword-id` int(20) NOT NULL, 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`keyword-id`,`staff-id`,`department-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_departments_staff_mantis_tickets` ( 
  `id` int(6) NOT NULL, 
  `ticket-id` int(12) DEFAULT '0', 
  `ticket-subject-id` mediumint(30) DEFAULT '0', 
  `follow-up` int(12) DEFAULT '0', 
  `closed` int(12) DEFAULT '0', 
  `raised` int(12) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_emails` ( 
  `id` mediumint(30) NOT NULL, 
  `from-id` int(14) DEFAULT '0', 
  `subject-id` mediumint(30) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `content-key` varchar(44) DEFAULT '', 
  `attachments` int(6) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`content-key`(20),`from-id`,`subject-id`,`ticket-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_keywords` ( 
  `id` mediumint(20) NOT NULL, 
  `state` enum('actionable','historical') DEFAULT 'actionable', 
  `keyword` varchar(64) DEFAULT '', 
  `occurences` mediumint(30) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`keyword`(43),`state`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_messages` ( 
  `id` mediumint(30) NOT NULL, 
  `email-id` mediumint(30) DEFAULT '0', 
  `subject-id` mediumint(30) DEFAULT '0', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `message-id` varchar(64) DEFAULT '', 
  `from-id` mediumint(30) DEFAULT '0', 
  `when` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`email-id`,`subject-id`,`ticket-id`,`message-id`(32)) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_names` ( 
  `id` int(14) NOT NULL, 
  `name` varchar(198) DEFAULT '', 
  `uid` int(11) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`name`(18),`uid`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_relayed` ( 
  `id` mediumint(30) NOT NULL, 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` int(18) DEFAULT '0', 
  `department-id` int(6) DEFAULT '0', 
  `mantis-node-key` varchar(44) DEFAULT '', 
  `mantis-ticket-id` int(14) DEFAULT '0', 
  `mantis-project-id` int(14) DEFAULT '0', 
  `mantis-assigned-to` varchar(64) DEFAULT '', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`ticket-id`,`staff-id`,`department-id`,`mantis-node-key`(16),`mantis-ticket-id`,`mantis-project-id`,`mantis-assigned-to`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_subjects` ( 
  `id` mediumint(30) NOT NULL, 
  `subject` varchar(300) DEFAULT '', 
  `email-id` int(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`subject`(30),`email-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_tickets` ( 
  `id` mediumint(30) NOT NULL, 
  `state` enum('new','waiting','resonded','mantis','ignored','spam','allocated','claimed') DEFAULT 'new', 
  `ticket-key` varchar(20) DEFAULT 'XXX-00000001AA', 
  `subject-id` mediumint(30) DEFAULT '0', 
  `from-id` int(14) DEFAULT '0', 
  `from-uid` int(11) DEFAULT '0', 
  `belong-uid` int(11) DEFAULT '0', 
  `belong-gid` int(11) DEFAULT '0', 
  `tags` varchar(255) DEFAULT NULL, 
  `created` int(12) DEFAULT '0', 
  `responded` int(12) DEFAULT '0', 
  `sent` int(12) DEFAULT '0', 
  `closed` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`ticket-key`(15),`state`,`subject-id`,`belong-uid`,`belong-gid`,`from-id`,`from-uid`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_tickets_attachments` ( 
  `id` mediumint(30) NOT NULL, 
  `state` enum('from','sent','mantis') DEFAULT 'from', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `ticket-contents-id` mediumint(30) DEFAULT '0', 
  `file-key` varchar(44) DEFAULT '', 
  `file-name` varchar(255) DEFAULT '', 
  `file-path` varchar(255) DEFAULT '', 
  `bytes` int(11) DEFAULT '0', 
  `when` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`ticket-id`,`ticket-contents-id`,`file-key`(19),`state`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_tickets_contents` ( 
  `id` mediumint(30) NOT NULL, 
  `state` enum('from','sent','mantis') DEFAULT 'from', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `content-key` varchar(44) DEFAULT '', 
  `by-id` int(11) DEFAULT '0', 
  `by-uid` int(11) DEFAULT '0', 
  `when` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`ticket-id`,`content-key`(24),`state`,`by-id`,`by-uid`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_tickets_ownership` ( 
  `id` mediumint(30) NOT NULL, 
  `state` enum('new','waiting','resonded','mantis','ignored','spam','allocated','claimed') DEFAULT 'new', 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `staff-id` int(18) DEFAULT '0', 
  `department-id` int(6) DEFAULT '0', 
  `when` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`ticket-id`,`state`,`staff-id`,`department-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8; 
 
 
CREATE TABLE `please_to` ( 
  `id` mediumint(30) NOT NULL, 
  `ticket-id` mediumint(30) DEFAULT '0', 
  `address-id` int(14) DEFAULT '0', 
  `name-id` int(14) DEFAULT '0', 
  `email-id` mediumint(30) DEFAULT '0', 
  `created` int(12) DEFAULT '0', 
  PRIMARY KEY (`id`), 
  KEY `SEARCH` (`address-id`,`name-id`,`email-id`,`ticket-id`) 
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Which will change before the final first release.. I am looking for volunteers for the translation of the language files as well if your around bleekk (who did all the mail templated in XPayment) or someone to write some mail templates and give a hand with the other templates, you will be dually noted in the code stamp...

Just get in contact with me through the email address on here or my listed skype account, you can see here when logged in!

5655

Re: TDMCreate 1.91 alpha 1 for Testing

2015/6/29 12:26
timgno
Module Developer
Posts: 1504
Since: 2007/6/21

I've released a patch

5656

Re: TDMCreate 1.91 alpha 1 for Testing

2015/6/28 21:24
Mamba
Moderator
Posts: 11373
Since: 2004/4/23

Quote:

Release alpha 3.3 is available
Test code passed by scrutinizer with quality 7,47

Timgno, you really need to add to your "test checklist":
- test a fresh install before release

This is what I am getting:

 Unable to install tdmcreate. Error(s): 
Installing TDMCreate 
 
Column count doesn't match value count at row 1

I appreciate very much your hard work and dedication, but this is like the n-th time happening that you release a new version and we cannot even install it, and we've talked about it several times already

Create a Codeception test for fresh install and uninstall of the module, and run these tests before a new release (plus all the other tests), and this issue will never show up again!

Let us know once this is fixed...

Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

5657

Re: TDMCreate 1.91 alpha 1 for Testing

2015/6/28 20:46
timgno
Module Developer
Posts: 1504
Since: 2007/6/21

Release alpha 3.3 is available

Test code passed by scrutinizer with quality 7,47

Refactoring code.

Needed more tests

5658

Re: Images width

2015/6/28 10:12
Zirafka
Just popping in
Posts: 70
Since: 2008/8/9 1

Thank you very much :)

On IE 8 is all ok. IE 11 I will be tested on monday.

I put the data into the file "styleIE8.css", because Opera and Firefox show images correctly.

5659

Re: Images width

2015/6/28 9:40
brutalicuss
Not too shy to talk
Posts: 128
Since: 2012/6/9 1

tray in .css
img {max-width: 100%;height: auto;width: auto \9;}
if not, set for your content
.item img {max-width: 500px;height: auto;width: auto \9;}

5660

Re: Images width

2015/6/28 4:53
Zirafka
Just popping in
Posts: 70
Since: 2008/8/9 1

Sorry, I forgot. Mea culpa.

I tested on my home computer with Windows XP + IE 8 and on friend computer with Windows 7 + IE 11. Problem is same.

May be a problem with IE settings?

Stats
Goal:	$100.00
Due Date:	Jul 31
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Re: TDMCreate 1.91 alpha 1 for Testing

@required::- Complete support of xoops_version.php module info in about dialogue!

Suggest DVD/CD Database

Xoops Module ~ Please ~ Email Ticket's with Keyword(s) Grouping Supportives

Re: TDMCreate 1.91 alpha 1 for Testing

Re: TDMCreate 1.91 alpha 1 for Testing

Re: TDMCreate 1.91 alpha 1 for Testing

Re: Images width

Re: Images width

Re: Images width

Login

Search

Recent Posts

PHP 8.4.0 Alpha 1 released

Overview of the Composer packages in Admin

Re: xoops_getBaseDomain

xoops_getBaseDomain

Re: Test 3

Test 3

Re: Test2

Re: Test2

Re: Test2

Test2

Who's Online

Donat-O-Meter

Latest GitHub Commits

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