Quote:

Never doubted you for a minute Darcy!

I'm concerned we're going to have XO for much longer. Sounds like the fighting over servers and backups has begun elsewhere. Oh well, we'll find a home SOMEWHERE if XO goes.

I've always liked your Wiki!

Quote:

Nope... no other errors. Just a blank page. It's on an intranet site, or I'd give you a URL to look at it. It's a wierd one... I saw the function above where it says the error occurs, but I couldn't see anything wrong with it. Dunno..

Quote:

Yup.. I'm on the latest. Upgraded to try and fix the problem. No joy...

Quote:

Put me on your list as agreeing 100%. The XOOPS concept was so beautiful back in 2003, and it's been tarnished again and again by pettiness and bickering. It's actually painful now to come to this site (when it's up). And now, hearing about the betrayal by the latest of the never ending re-org teams, I'm to the point of throwing the whole thing out.

Quote:

Actually, that's the problem. They don't know who they are. All of the real trouble makers have been quietly working their covert agenda, snowing us into believing that they were working in our benefit on our beloved Xoops. The blowhards have been serving their unknown masters well by dividing us and allowing them to take advantage of the work of so many to create their own #OOPS#ized fork of Xoops. Any real person with feelings for anyone besides themselves would feel BADLY about the whole ImpressCMS mess, and trying to "Serve two Masters" as Jesus put it.

It's time for some righteous indignation on the part of those of us who humbly TRY to help the program along, and who want to approach the XOOPS CMS in a more professional way. It's time for us to call for an ELECTED group to run the XOOPS program, and for ACCOUNTABILITY to be the word of the day.

I fear we'll never see it. I hope we will, but I'm betting we won't.

Quote:

Man.. chisel that in stone! Being a not-so-technical (my PHP knowledge sucks) user of XOOPS for several web sites, and attempting to use the software in a business environment, I haven't had much to input here. Partially due to time constraints, and partially because I just don't have that many answers.

I try to help when I can by Wiki or Forum postings, but there is a lot more I could do, and like many here SHOULD HAVE DONE to assist the efforts in the past.

I believe that XOOPS is dead unless it can put together a cognizant plan for going forward in the future. We need leadership. We need organization. We need persistence and understanding. We need to renew our sense of community.

Without these things, the millions of keystrokes we have all made here mean nothing.

How do we do it? We focus on Xoops. We ignore the forks and let them do their thing just as we are going to do ours. The nefarious way that the current board has been acting is grounds for dismissal clearly.

I don't know about all of you, but the new XOOPS site is pretty much the OLD XOOPS site. I see no improvement to speak of. The module/theme repository continues to have broken links, old modules and themes and is disorganized to say the least. It needs an enema.

Further, it's now clear that one of the reasons for the slow development of Xoops, and the poor re-building of this site is that there was a DISTRACTION taking time away from Xoops, and putting it into a fork of Xoops. There's a lot of detail elsewhere in the forums on what's been going on, so I won't go into it here, but.... THE EMPEROR HAS NO CLOTHES! We've all been had.

Giving up and throwing in the towel was my first thought, but then I got angry, and decided to make XOOPS a success as my PERSONAL choice by doing everything I can to help in the future.

So, I'm committed... who else is committed with me?

Hello all,

I've run into an interesting one that has got me scratching my head. I've read the blank page FAQ, and I've checked for that, but I'm having a weird problem I can't figure out. Any help would be appreciated.

Configuration:

XOOPS Version: XOOPS 2.0.17.1
XOOPS Theme: default
XOOPS Template Set: default
PHP Version: 5.2.4
MySQL Version: 5.0.45-community-nt
Server Software: Apache/2.2.6 (Win32) DAV/2 mod_ssl/2.2.6 OpenSSL/0.9.8e mod_autoindex_color PHP/5.2.4
User's Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Problem Symptoms:

With the Article 1.00 Final module installed (new install), and with blocks from the module (any of them) set for the Top Page, when logging into the URL of the Home Page (or Top Page) all that is displayed is a blank page, indicating an aborted script. Setting the block(s) to display on the Article module pages works fine. Returning the blocks to the Top Page (or adding Top Page to config) will immediately blank the home page again.

Debug Mode Error Codes:

Fatal error: Call to undefined function art_formatTimestamp() in D:\xampp\htdocs\modules\article\include\functions.parse.php(133) : eval()'d code on line 140
All errors (4) queries (109) blocks (31) extra (0) timers (4)

Code from that section (Line 140 -2 and +2):

Quote:

Obviously, this is comment code, so the error is being reported on the wrong line. I can't figure out whether the function above the comment is broken, or the one below it.

Any help would be appreciated. This is a great module, but I really NEED the blocks to work on the Home Page. Thanks in advance all you Xoopsers!

Byron

Quote:

The Church site works, but your link to kavaxtreme.radiantchristians.com does not! I get a blank page, and blank page source in Firefox 2.xx. Do you run Protector module? If so, that's probably 90% of why it's not working. I've had protector lock EVERYONE out of my site at once in the past.

It's not a DNS issue, as your site pings just fine, and http does connect to your server according to DNS lookup utils. It may also be a 301 forwarding issue of some sort. Don't know...

Is there a secondary location to download the theme?

BAM

Quote:

That's only if they READ the question to begin with. They only read the questions if they have already figured out how to make money on reading them!

BAM

Quote:

Actually, it's more like XOOPS is Slackware Linux, and Joomla is Ubuntu... The Windows CMS is YET to happen IMHO...

BAM

Have you looked into any of the menu expansion modules available. Sorry, having a brain fart as to names of some... but basically there is a multi-menu module that allows you to build up to 8 I believe menus and put them anywhere as blocks. That may help you to break it up some. The other thing you could do is build a center center block, and just build html links like we used to do in the old days ([link], [link1], [link2], etc.). That would give you one heckuva lot of link space. But I gotta ask... maybe a section module if it's all content may be more appropriate yes? Are all of your menu links to Modules or content?

You are comparing apples and oranges.

Xoops is, from it's name on down, a "programmers content management system". Who else but programmers would put Object Oriented in the name of software intended to eliminate programming for the actual users of it? Programmers drive the team. Programmers have written all the code. Programmers have had all the arguments and version hassles that have fundamentally put XOOPS on semi-permanent hold now for over a year.

Xoops requires a LOT of tweaking (it didn't used to, but that's another diatribe for another day) to get it working, and even more hassles to locate documentation, modules, blocks, and all the little widgets to make it happen. It takes me a week to get a XOOPS site fundamentally operational. It takes me a day to get a Joomla site in the same state. (Spoken as an integrator for both).

The end result can be very rewarding though. XOOPS modules, when you can get them to work with the version of the day, usually offer more, and better done than Joomla equivalents.

I disagree with the comments made earlier with regard to there being more available with Joomla. I have collected everything there is to collect (both legally and not-so-legally) for both XOOPS and Joomla, and have found that you have to eliminate a LOT of the Joomla offerings because they are proprietary (cost you money), and usually VERY pricey. You have to eliminate some more for the same reasons as XOOPS - the VERSION problems (Joomla now has it's own version of XOOPS 2.0.x versus 2.2.x zoo in their 1.1.x and 1.5.x versions, which are COMPLETELY incompatible module wise and even to a great extent in template/themes!). What you are left with is a pale comparison to what is available with Xoops.

Joomla is administrator and end-user focused, and is attempting to bury as much of the programming as it can, hiding it from the people who will actually have to work with the interface. It is also (as you have discovered) highly graphical and end-user functionality oriented. They "get" what a content management system is about - Ease of administration, ease of authorship, workflow creation and maintenance, and flexibility.

Joomla has more of a business focus, but with the Community version (look it up on the Joomla.org site) they have an off-shoot version that blows XOOPS away at building city, county, church, organization, fraternal or whatever communities all in one package right out of the zip file.

In the best of all possible worlds, I could put both XOOPS and Joomla in a bag... shake it up, and pour out.... Xoomla... a hybrid with the best of both CMSs in it. The fact of the matter is that all CMSs by the nature of what they do are compromises. In some places each compromises too much, and too little.

As to the communities and support. I'd have to say that at the moment, Joomla is kicking the slats out of Xoops. Their .org site is neat looking, well organized, easy to find things on, current (for the most part), pretty well documented, and all of it is very tidy and graphically superior to Xoops.org.

Their forums suck. It takes forever for anyone to come back to you on questions. Very few people will stick their two cents in (like I am doing here). The "businesslike" manner is not to most hobbiest mentalities either necessary or welcome. You'll see for yourself.

My personal complaint with Joomla is that is violates "the code" of Open Source so often it's not funny. Everyone over there thinks they are going to write 50 lines of PHP code, encrypt it with Zend, and get rich. As Mr. Bush says, "Isn't going to happen!". They condone way too much advertising in their site, and let modules be sold that are basic core modules in my opinion.

Xoops is flawed. It's had some hard knocks (hacked .org site, hardware failures, rapid team dropouts and replacements, and lack of focus recently), but it "persists", and overall, it is for the most part reliable once installed and running. The variety and quality of modules cannot be questioned. The validity of them with current versions unfortunately can.

Both Joomla and XOOPS have their problems. Both have thier strengths. Kind of reminds me of the Monty Python bit "Peoples Judean Front" versus the "Peoples Front of Judea".

I use XOOPS when the site I am building is going to be more customized, and more technical (code wise, not graphically). I use Joomla when a site needs to be more graphical, and more community oriented.

They BOTH frustrate me. XOOPS frustrates me a little more because in my opinion, with shaping up, it has far greater potential than Joomla. But it's falling so far behind because of this 2.0.x versus 2.2.x thing, and the squabbling and behind the scenes changes that may ultimately force those of us who love the thing to just abandon it.

What the XOOPS Team needs to do IMHO... sit down with some administrators, AND end user/author types who are currently using Xoops, and ASK THEM what's screwed up and what's brilliant (I know I have MY list). Then form a list, then form a plan, then start implementing it, then honor the plan to completion... REPEAT. The .org site needs an enema. There has to be someplace really really soon where ALL of the available modules, blocks, hacks, hints, tips, etc. are cataloged and available without having to go to 500 sites and register on every one of them to get at it. There needs to be ONE documentation site just like Joomla already has in both cases. When all of that is done, then I can clearly say "Go with XOOPS every time". Till then I'm leaning towards Joomla.

Just my opinion of course, your mileage may vary...