You're right, they are not counted.

Again, going to visit your site (http://mitjab.info/xoops-2.0.9.2/modules/news/) I can't see the javascript into the website source.

Hello senzaciona,

I can't see the javascript code which must be included into your theme.html file (when I edited your website source).
If this javascript isn't present, the module cannot function.

If you're certain that you've added it into your theme.html file, try to erase all files (or at least your *theme.html file) into the templates_c folder of your XOOPS website.

Now, for those which for some time have problems with this module whereas it functioned correctly until now, could you try to see if your webhoster has implemented the mod_security into the apache configuration?
If it is the case, this mod is breaking the module (the url calling by the javascript code is considered as an xss request). I'm actually working on this problem!

Hello Rhomal

I don't have enough time to resume all I said to Jensclas in the other THREAD...sorry. (I can't edit my previous post to correct the link!!??)

I see that you have put the portion of code but I introduced an error and it shhould be:

Instead of what the xoops2_install.txt said. (Did you noticed the difference -> istat.src = "<{$xoops_url}>/modules/istats/include/counter.php?.... instead of -> istat.src = "http://<{$xoops_url}>/modules/istats/include/counter.php?....)

Again, sorry for the inconvenience.

Kind Regards

[EDIT]
I have just seen that you have already corrected my mistake and that istats is now functional onto your website.
[/EDIT]

Hello Rhomal

You emailed me the same question like the one in your first post and answered you by giving a link to another post on xoops.org...this post.

Did you received it?
Is there something you don't understand?
I'm not joking about you or any others but, since Jensclas's posts, I realize that the xoops2_install.txt seems to not be as clear as I thought.

So if you need more explainations, I'll be yours.

P.S: As soon as I will have enough time, I will add a FAQ section onto my website about "all" the modules that I adapted.

Kind Regards

Quote:

I can't see your email address in your profile.
Maybe you could PM it to me.

Also I can tell you it is not a diretory permission problem but an echo with $variable['index'] that should look echo"...{$variable['index']}... (or something like this if I remember it well).

There are also some variables that are not Register_globals=Off compliant, the reason why some actions are not authorized... etc..

I don't understand how this module could be put on line in this state (I was not to be awaked)

Hello Hawkeyegop

I remember to have debuging it for the same problems onto XOOPS FR.
Unfortunately the links where all are the posts seems to be broken.

If you want I could send it to you by email.

Hello Jenny

I'm really confused because I introduced an error into the javascript code you have to add into your theme.html file.

If you use the first option and so decide to add the code into the theme.html, you have to add this before the closing tag </body>:

Did you see the difference? There isn't the 'http://' before the smarty variable (istat.src = "<{$xoops_url}>....) because it already has it!

Now my second error is with the option two.
I haven't tested before the possibilty of adding the same javascript code into the meta/footer section of xoops!
So I just realize that <{$xoops_url}> is not interpreted.
The code you have to add with the option two is:


I don't know what to say more...maybe nothing and rather than saying other silly things, it would be better for everybody that I go to sleep.

Now to answer to your several questions:

1 - Because rather than using files into the templates_c folder (a cache) XOOPS will always going to read your theme files into your theme folder and each files will need to be parsed by smarty (more time consuming). (Others can tell me if I'm wrong, I will take no offences. )

2 - You can do such things with your site opened.

3 - You can do this without risks, each file will be rebuilt at the time of its next call.
But if you are really afraid, you can seek only the file(s) *theme.html and erase them/it.
Please note that you don't need to do this if you turn to Yes the option 'Update module template...'.

I hope that this time will be the maid for you and istats and that you will see finally this module functioning.


Sylvain (too tired )

Hello Nuker

Maybe I'm totally wrong but I had some similar problems with my apache server and fedora core 3 and not with mandrake.

The thing was that apache was unabled to write or to read some files even if the good permissions were there.

While making research, I was directed towards protection via SELinux included in fedora.
So I had disabled it for the httpd process and now all is fine.

Hello Jensclas

You've given me a simple but efficient lesson on how to make a good support.

I'm sorry not to have written that but rather to realize that the xoops2_install.txt is not clear enough for newbies.

I want to also add that if you had mentioned that research that you had made had not been effective to answer your questions, I would probably not have begun my response in this way.

But what is fact is made then pass to your problem.


First option

You were right when you had put the javascript code like this:


Now I can see that you have the same code between the </head> and <body> tags:


Don't forget that all changes into your theme.html file will not take effect until you have done the last point I mentioned:
Quote:


Second option

By the way, I realize that your theme is using a usefull smarty variable ->> <{$xoops_footer}>.

So you can try another thing:
Go to System Admin -> Preferences -> Meta Tags and Footer and click [Edit].
There, copy the javascript code:

and paste it into the Footer section below what already exist so you should have this:


It'll be simpler but if you change your theme and if it doesn't have the smarty variable <{xoops_footer}> you will have to do the first option.

I hope it is clear enough...at least not to confusing!

Still sorry if I wounded you, it was not my intention.
My English is rather old, I learned it 17 years ago, and I rely sometimes on Google which is not always effective.

Friendly