Deprecated: Assigning the return value of new by reference is deprecated in /home/canada/subdomains/xoops/modules/newbb/viewtopic.php on line 582

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 49

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsLoad::loadCoreConfig() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 91

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/class/preload.php on line 28

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/class/preload.php on line 29

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsPreload::getInstance() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 50

Strict Standards: Non-static method XoopsCache::read() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/preload.php on line 85

Strict Standards: Non-static method XoopsCache::getInstance() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/cache/xoopscache.php on line 263

Strict Standards: Declaration of XoopsCacheFile::write() should be compatible with XoopsCacheEngine::write($key, &$value, $duration) in /home/canada/subdomains/xoops/class/cache/file.php on line 308

Strict Standards: Non-static method XoopsLoad::load() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/cache/file.php on line 110

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsFile::getHandler() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/cache/file.php on line 111

Strict Standards: Non-static method XoopsFile::load() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/file/xoopsfile.php on line 108

Strict Standards: Non-static method XoopsLoad::load() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/file/file.php on line 105

Strict Standards: Non-static method XoopsFile::getHandler() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/file/file.php on line 106

Strict Standards: Non-static method XoopsFile::load() should not be called statically, assuming $this from incompatible context in /home/canada/subdomains/xoops/class/file/xoopsfile.php on line 108

Warning: /home/canada/subdomains/xoops_data3/caches/xoops_cache is not writable in /home/canada/subdomains/xoops/class/cache/file.php on line 302

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 60

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 68

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 75

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /home/canada/subdomains/xoops/class/xoopsload.php on line 71

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /home/canada/subdomains/xoops/include/common.php on line 76

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /home/canada/subdomains/xoops/class/logger/xoopslogger.php on line 374

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /home/canada/subdomains/xoops/class/logger/xoopslogger.php on line 374
a suggestion regarding the user to commit to the event [Forum for APCal - Report...

Antiques Promotion Canada

Community for Collectors & Canadian Antique Dealers

Canadian antiques dealer, collectors Antique Dealers

Map of Canadian Antique Dealers

Antique shows, auctions houses, collectors clubs and markets

Finding a Canadian antique dealer has never been easier. Plan your trips and find fabulous antiques & collectibles using our antique resources map of Canada.

AP site: AP Encyclopedia AP Forum Articles Classified Ads Map & Directory of Antique Dealers Calendar Book Search Poll


This site: Home Download Forum Demo Contact us

 Login
Username:

Password:

Remember me



Lost Password?

Register now!
 Search
 Who is Online
20 user(s) are online (1 user(s) are browsing Forum for APCal)

Members: 0
Guests: 20

more...

Browsing this Thread:   1 Anonymous Users


 Bottom   Previous Topic   Next Topic  Register To Post



a suggestion regarding the user to commit to the event
Just popping in
Joined:
2015/11/4 0:07
From Pereira
Group:
Registered Users
Posts: 2
Level : 1; EXP : 2
HP : 0 / 0
MP : 0 / 8
Offline
Add the possibility that not only the user signs but can also commit to the event object would give the event a large program of funicionalidad who has now lost. Before events related modules allow its use for appointments, consultations, appointment reservations, interviews, limited quotas attending an event. But he hoped that with its full functionality and APCalendar also had it is not. And it is simple, it is adding the possibility of having ownership of quotas, limited or not. And the possibility of the user object has the property engaged or not the event. Even an event, such as oor attention of a professional, could only allow a user to be full. I'm talking for example, appointment scheduling queries to a professional. Thank you.

Posted on: 2015/11/4 0:37
Transfer the post to other applications Transfer


Re: a suggestion regarding the user to commit to the event
Just popping in
Joined:
2015/11/4 0:07
From Pereira
Group:
Registered Users
Posts: 2
Level : 1; EXP : 2
HP : 0 / 0
MP : 0 / 8
Offline
excuseme my handler error, please replace "funicionalidad" by functionality

Posted on: 2015/11/4 0:40
Transfer the post to other applications Transfer




 Register To Post


You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.

[Advanced Search]