51
RicoCali
Re: Error: Could not open lock file
  • 2003/12/9 1:47

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Oh sorry CBLUE for the confusion. I'm having problems with the XOOPS 2.0.5.1 version using the current virgin of xoopsgallery 1.3.3.3 fromhttp://www.sciox.org/xoops/modules/news/. What I was saying was that I don't have any problems with it using XOOPS 1.3.8 that uses the gallery program that works with 1.3.8



52
RicoCali
Re: Error: Could not open lock file
  • 2003/12/8 18:12

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Just anothere note... The gallery stuff works in a XOOPS 1.3.8. So I don't think the NETPBM and IMAGEMAGICK stuff have any problems. It has something to do with the software I downloaded from sciox.com and XOOPS. I just don't know what it is



53
RicoCali
Re: Controlling Center Block Positions with Top Page Module
  • 2003/12/8 0:15

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


I think I owe a lot of you folks a beer at a pub. Thank you for your help Horacio...very much appreciated.



54
RicoCali
Controlling Center Block Positions with Top Page Module
  • 2003/12/7 21:32

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


I have specified to use wfchannel default page to be at the TOP of my opening page and NEWBB RECENT POST block to be in the center. The problem with this is that I don't have any control to put the WFCHANNEL module to appear "first" in the center and then show NEWBB RECENT POST block. Anybody got any suggestions?

Thank you,
Rico



55
RicoCali
Where is the WYSIWYG in current version of WFSECTIONS
  • 2003/12/7 21:24

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


I used a previous version of wfsections for XOOPS v 1.3 and it had the full blown WYSIWYG editor and thought that it was pretty slick. Is there any reasons why the WYSIWYG editor has been discontinued in the current version of wfsections?



56
RicoCali
Re: Error: Could not open lock file
  • 2003/12/7 21:21

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Quote:

jlm69 wrote:
Maybe check your php info to see if exec() is enabled.


I don't know where that is in phpinfo() but if you mean being able to run:

$output = shell_exec("ls -l");
echo $output;

or

$output = exec("ls -l");
echo $output;

...they both work



57
RicoCali
Re: Proposal for an XOOPS standards committee
  • 2003/12/7 21:01

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


It's nice to hear that this is already thought of. I stay tuned to whats going on with PHPNUKE and its evolution. It's a hacked paradigm. As it grows it will be almost impossible to maintain. Also, I spoke to someone in this community that mentioned that "anyone can build a module and intentionally leave some security holes to fit their agenda". That scares me because if the module is never scrutinized, the author can interogate a heavy traffic site and get any information he/she wants. The developers are always on top of security issues for XOOPS. But what is blindly overlooked are the third party modules. Who is scrutinizing that? I think the third party module developers should continue to do whatever they are doing and people that like their stuff should continue to do whatever they want to do. But for other people that want an "official" label in what they use should also have that option.



58
RicoCali
Re: Error: Could not open lock file
  • 2003/12/7 18:11

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Quote:

jlm69 wrote:
<?php
echo ini_get("disable_functions");
?>
If the output displays exec() see FAQ C.29.


Well I tried that and it didn't output anything back.



59
RicoCali
Re: Error: Could not open lock file
  • 2003/12/7 15:30

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Its my own server and I've chmod 777 everything recursively. Its in the right path. If the path is wrong it give you a different error. I tested it. So I am clueless with all this hokus pokus.



60
RicoCali
Proposal for an XOOPS standards committee
  • 2003/12/7 12:02

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


The XOOPS community is growing and I see more and more modules out there and hard to decifer which ones I should even consider. The other problem that I'm beginning to se are forks and hybrids of the original modules. This is a long process because you have to determine if its written as an "official" fit for XOOPS. Smarty, use of core classes instead of reinventing, standard procedures, etc... I know there is a "VOTE" thing for modules and themes but thats not good enough. It would be nice if an XOOPS committee gives an "OFFICIAL" stamp for modules. I'm not encouraging other modules to go away...I want them to continue as is.




TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 11 »



Login

Who's Online

252 user(s) are online (158 user(s) are browsing Support Forums)


Members: 0


Guests: 252


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