293841
schwim
Re: Is XOOPS used for business applications?
  • 2002/7/27 6:24

  • schwim

  • Just popping in

  • Posts: 11

  • Since: 2002/7/25


I would agree that XOOPS is much more robust in many respects than PHP-Nuke. I've just moved over due to a db crash caused by phpn. I had been looking at XOOPS for a few months, and when this happened, it seemed like the perfect time to try it.

I like the fact that current bugs are actually squashed before creating new gadgets with more bugs in them. It's so refreshing to install this CMS and have no errors when accessing it for the first time!

Thanks for the great script!
Jason



293842
w4z004
Re: PhpAdsNew
  • 2002/7/27 4:34

  • w4z004

  • XOOPS Advisor

  • Posts: 340

  • Since: 2001/12/13


yup, later of activated need "install"



293843
w4z004
Re: PhpAdsNew
  • 2002/7/27 4:33

  • w4z004

  • XOOPS Advisor

  • Posts: 340

  • Since: 2001/12/13


and later of activate need "install" the module.

is a "stand-alone" php script , you right because are not integrated the user / passw and because this are actualized all time by the phphadsnew team.

i;m are only modularized for this can appear into the admin part of XOOPS nothing more.

the script remain how a stand-alone.

and think: the XOOPS banners need a separated login for the clients - in phpadsnew is the same
and only need log to the admin part (we can hack this but all time are changed the phpadsnew and is a lost of work) is better have in stand-alone ,
And phpadsnew is not for all the sites, is for intensive use.



293844
Jan304
Re: PhpAdsNew
  • 2002/7/26 17:57

  • Jan304

  • Official Support Member

  • Posts: 520

  • Since: 2002/3/31


No, it doesn't work with only activating it. Just like w4z004 said (I just think what I should do-, activate module, run install script, (admin/admin-generate.php), you can prefer your own code, the put it the code in every theme.php you've from your themes.



293845
smackdaddy
Re: PhpAdsNew
  • 2002/7/26 17:40

  • smackdaddy

  • Just popping in

  • Posts: 14

  • Since: 2002/3/28


w4z004,

Let me see if I understand correctly.....

phpAdsNew can be used in XOOPS just by placing it in the modules folder and "activating" it? I thought it was a stand-alone PHP script.....that's where I got confused...

I have looked at their EXTENSIVE manual and did not find anything in there about XOOPS integration, so I would hope you could let me know how to get it active and the best way to get it to work.....

Thanks much!



293846
MaxIT
Re: Account re-activation required on Profile email changes
  • 2002/7/25 12:39

  • MaxIT

  • Just popping in

  • Posts: 65

  • Since: 2002/11/8


Quote:

goghs wrote:
Yes this makes sense.
Maybe we can add the logic like this:
when a user changes his email, his account will be disactivated, and then an email with activation code will be sent to his new email.
It can be an option.


A doubt came in my mind thinking about this logic: if you disable a user when he change email, waiting for a new activation click, what will happen if user has written a wrong email?

Whith this logic, his/her account will be disabled, and as long as he will not receive that new activation email sent to a wrong address, the user account will remain disabled!

possible solution:

- when user change the email address, the new activation code will be sent to both new & old email address.



293847
dscg
Re: Browser cache causing many problems?
  • 2002/7/21 6:13

  • dscg

  • Just popping in

  • Posts: 9

  • Since: 2002/6/7 8


I found the no-cache HTTP header commands for the browser not to cache pages in the header.php file in the XOOPS main directory. So browsers should not cache any XOOPS page that include the root header.php file.

However, there are instances where you may call the redirect_header() function BEFORE including the header.php file in the root directory. This commonly occurs when you check if the user is logged in at the start of your module code like this Quote:
if ( !$xoopsUser ) {redirect_header(...)}

include $xoopsConfig['xoops_url']."/header.php";
... continue with the module code...


The problem is that the redirect_header() function does not have the HTTP no-cache commands. Therefore, the browser caches the redirect page. This has caused me many problems with users not being able to access pages even when they have permission to do so.

My suggestion would be to include the PHP header() function with the no-cache and expire commands in the redirect_header() function as well.

Otherwise, you will need to go through all the files to makes sure that $xoopsConfig['$xoops_url']."/header.php" appear before your redirect_header() call to avoid browser cache problems.



293848
Anonymous
Re: BUG when tables in Forums or News
  • 2002/7/19 20:28

  • Anonymous

  • Posts: 0

  • Since:


Yes its a bug and being looked into



293849
Phifou
Re: BUG when tables in Forums or News
  • 2002/7/19 18:26

  • Phifou

  • Just popping in

  • Posts: 6

  • Since: 2002/6/6 9


It is a fact to say that it is a XOOPS BUG...

Neanderthal PHP-Nuke does not have this problem ...



293850
Anonymous
Re: BUG when tables in Forums or News
  • 2002/7/19 17:10

  • Anonymous

  • Posts: 0

  • Since:


Of course not

DW is pretty cool, but for now you don't really have the choice
Remember this is a RC(release candidate) so it's not final and still has many things left to be corrected in it.







Login

Who's Online

197 user(s) are online (164 user(s) are browsing Support Forums)


Members: 0


Guests: 197


more...

Donat-O-Meter

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

Latest GitHub Commits