I prefer to use it in the header, but footer is better for loading times.
All in all, I think it comes down to personal choice.

Hi All,

Where do you include your Javascript. Do you include it in the HEAD or right before the closing BODY tag?

or does it depend.

I'm doing my best to contribute, Bleekk, but everything takes time :P
I've started yesterday to modify the wiki, started making templates, writing articles and more.

I've also started working on a new theme, which is coming together quite nicely for the few hours that I've been working on it. It still needs a ton of work, as I'm likely going to modify all of the templates to make sure everything looks and reacts like I want to, but in general I'm glad with the result!
It's based on xBootstrap, which in my opinion is the best base theme you can get.
Here's an image of how it's looking right now
(click for full image).

Feedback is welcome :)

I also think that nobody want to bash certain user. There is no reason for that because they are doing all a wonderful job.
But everyone is free to make suggestion how things can be improved.

Xoops is a community product and I hope that we all together can make a contribution to make it better.

Michael, I'm not here to bash XOOPS, but I've noted things that stopped me before from helping. I'd like to help, starting immediately, with several things:
* Documentation. It's the thing that we need most of all. The problem that I have with Gitbook is stated in a post above, namingly no global search (which is really needed). We don't need a collection of ebooks, we need a central place of information that is easily searchable.
While I'm typing this I was trying to figure out if I can do something with the current wiki in place, but it's hard to find a starting point.

* Cleaning up the repository/theme gallery/forums. I'd like to help with this too, but right now I can't. Is there an easy to find list with updated modules right now? We should put a notice on top of the module repository that points to that list.

If you can point me the right way with this, I'll help instantly as much as I can.

Quote:
Kevin, I'm sorry, but I don't get it!

If it really "breaks your heart", what are you going to do about it? In which area are you going to help XOOPS?

Do you really think that your rant is very helpful? Do you really think that we don't know about the issues we have? For example, you complain about Documentation, but we know about it forever! If you would spend some time looking around XOOPS instead of jumping to conclusions, maybe you would see this recent News about Documenation, and you would see that we are doing something about it!

I have stated there very clearly:
Quote:
For people who would like to help, I have documented the "XOOPS Documentation Process", and have created a "XOOPS Docs Starter Kit". And I have updated bunch of documents and tutorials.

Honestly, XOOPS will benefit more from people who are willing to write new tutorials and help us with other documentation, than from people telling us that we don't have tutorials! Because we already know it! Come on, Kevin - do you really think that we are so stupid or naive that we don't know it?

I find it unfair and even disrespectful to people like Richard, who is working around the clock to get XOOPS 2.6.0 move forward, and you can see the progress of over one year in 45 seconds.

Unfair to people like Eduardo who has created the awesome Common Utilities, and now is working on integrating it into XOOPS 2.6.0.

Unfair to people like Angelo who created xBootstrap, and Bleekk and Heuyla, who helped him to create templates for several of our modules.

Unfair to people like Luciorota or Zyspec who are working on updating several of older modules.

Unfair to people like Cesag who worked tirelessly on translations!

The reality is that yes, we are short on manpower. And therefore we need to focus and prioritize. As a result, some less critical issue will be placed on back burner!

We haven't publish recently "WOX: World of XOOPS", because it was less critical for me. Instead, thanks to Richard and few other friends of XOOPS, we have immediately fixed all security issues we've been made aware of, and we we have upgraded XOOPS so it is fully compatible with the latest PHP 5.6 version. For comparison, go ahead and try to run some of the XOOPS forks or even other Open Source CMS on PHP 5.6.

We have published pretty much consistently every 12 months a new releases of XOOPS, incl. security updates:

2012/04/16: XOOPS 2.5.5
2013/04/28: XOOPS 2.5.6
2014/06/16: XOOPS 2.5.7
2014/11/24: XOOPS 2.5.7.1

And we probably will publish XOOPS 2.5.8 in the spring of this year.

All of this while continuing work on XOOPS 2.6.0, with some major architectural changes which will help XOOPS to finally catch-up to the other mainstream CMS solutions.

We also try to keep our current users happy by providing help and support on the Forums, and by updating modules as much and as fast as we can. For example, all the most popular modules have been converted to "Blue Move Admin GUI", so they have consistent "look and feel". We are now in the process of streamlining several of the modules into a "Module Pack", and refactoring them so there is a higher reuse of common components between the modules.

Yes, Kevin, we are in some areas behind (like the WOX or the module repository), and we are missing some of the fancy bells and whistles there. But if you take the time to study the updated by Richard XOOPS 2.6.0 Roadmap, you will see that that we're aware of it and we're doing something about it.

Of course, XOOPS would benefit from help, and I was very happy to see you back, as I told you in my email! But since we are an Open Source project, it is really up to people like YOU, Kevin! You have the choice: you can come and bash us, or you can just help us to make XOOPS better!

The choice is yours!

Something which should also (in my opinion) be deleted is the Xoops Forge (http://dev.xoops.org/). It hasn't been used in ages and is kind of useless right now.

I suggest we create 1 central pool of documentation instead of the multiple sources we have right now: Xoops Forge, the XOOPS wiki on this site, the FAQ, Gitbook. It's simply spread in way too many locations.

An example of a system with great documentation is CodeIgniter (http://www.codeigniter.com/userguide3/), this is what all documentation should be: simple and easy to find the information with clear information.
In my opinion, Gitbook isn't really the solution we need because it has 1 huge disadvantage: search. Everything is separated in several different books, which means that you can only search in 1 book at a time. This is a huge disadvantage!

In my opinion a simple Wiki-approach might be best, but it looks to me that it would be better to use a seperate script for this. If we use a XOOPS module for that we risk that the module won't be updated which is really not what we want (and look at the MediaWiki module, it isn't updated often at all).

A seperate wiki has everything we need:
* Multiple users can work on it
* Everybody can contribute to it
* It is easy, everybody can do it
* Global search
* There are tons of good wiki's that show off that this is a good system
* History is kept and can be rolled back (abuse can be repaired)
* Not dependent on a third party service. Gitbook might be here now, but I've seen enough third party services shut down on a short notice to not trust them with something like documentation.

I'd like to hear the meaning of others about this though.

Hi!
Just built the largest XOOPS site I ever made. But with an expected 500000+ users end-of-year I would like for someone with excellent xoops knowledge to have a look at the website and share any thoughts and or find stuff that shouldn't be there :)
I'm not at liberty to share the website in public as yet, but the request has been made. It offers many addons specifically written for the website and thus for xoops.
Things like :
- stripe payment gateway
- facebook/google/twitter and other social network login and registration
- replacement of the PM module by a more What's up/skype kinda style messaging
with realtime updates and no popup.
- custom template driven registration
- complete themed publisher
- and 200+ hours more enhancements :)

It is at the point of going live and would really appreciate if someone could perhaps find vulnerabilities ?
If you have the time, and will, drop a replay and I'll pass on details.

Thanks!
Charly

Quote:

I fully agree with you that breaking with the past might be the best thing to do.
With the update to Smarty 3.1 and so much changes, it might be better to throw everything overboard. Most of what we have, with some exceptions, is severely outdated.
In this case I feel it's better to start anew rather than trying to update everything. That's just something with no end in this case.

Quote:

Luciorota, read my full message and you'll see what I can and will do for XOOPS ;)