xoops forums

Forum Index


Board index » All Posts (wingrider101)




wingrider101

Not too shy to talk
Posted on: 2009/8/24 7:18
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#11

News Module 1.63 with Xoops 2.4 beta - Blank Page when Submitting Article

Hi all... wierd problem that is probably my fault. First here are my system settings:

Xoops Version XOOPS 2.4.0 Beta
PHP Version 5.2.6-3ubuntu4.1
Mysql Version 5.0.75-0ubuntu10.2
Server API apache2handler
OS Linux
safe_mode Off
register_globals Off
magic_quotes_gpc On
allow_url_fopen On
fsockopen On
allow_call_time_pass_reference On
post_max_size 8M
max_input_time 60
output_buffering
max_execution_time 30
memory_limit 16M
file_uploads On
upload_max_filesize 2M

What I am getting is a blank page when I try to submit an article via the News Module's Submit command, and no button or anything below "Submit an Article" in the Module Admin submission. I've checked and double checked the module version (1.63 the latest directly downloaded from the home site), and de-installed and re-installed it several times with no luck.

Any thoughts on what it could be? What else do you need to know to troubleshoot?



wingrider101

Not too shy to talk
Posted on: 2008/10/12 16:17
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#12

Re: Block and Module "Weight" Values

I have a partial document that I'd like some of you guru types to look over. If you can send me an e-mail at my e-mail address. I'll send you back a copy of the OpenOffice odt file I have so far.

I'd love to have some comments/suggestions/finger pokes etc on how I'm doing.

Thanks in advance.

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/10/12 15:58
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#13

Re: 2.3.0 Final: Could not copy the distribution file to mainfile.php in installation screen 7/11

I solved the mystery! The mainfile.dist.php.protector has to be in the htdocs (root) directory, and you need to rename it to mainfile.dist.php FIRST before running install. If you use the mainfile.dist.php file that's in the distribution htdocs directory, you are ok. If you use the mainfile.dist.php.protector, you aren't. You have to rename it first for it to work.

Boy... the docs really don't explain that well.

Good to know though!

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/10/12 15:38
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#14

2.3.0 Final: Could not copy the distribution file to mainfile.php in installation screen 7/11

Could not perform the upgrade from 2.3 RC to 2.3.1 - instructions followed to the letter. Would not allow module admin to see newly added modules, no icons, nothing in the list, nada. So, since it's my own personal site for testing, I blasted the system and database (deleted all) and following installation instructions in the text file, put new 2.3.1 downloaded directly from the "forge" on the system.

Created new user/database in MySQL before install. Checked all permissions. Ran install, and everything goes fine until screen seven of eleven, where I encounter this:

Quote:
Saving your system configuration Could not copy the distribution file to mainfile.php


Re-checked permissions, and all is correct. I did use the mainfile.dist.php for Protector and rename it to mainfile.php prior to install. This is what the instructions said to do. My directory looks like this:

/home/byron/xoops_data
/home/byron/xoops_lib
/home/byron/www

where www is the htdocs directory. Install finds everything just fine and everything is green up to screen 7.

HUH???? OK, so what "distribution file" is it attempting to "copy". I already copied all of the distribution files into the appropriate directories. In the past, mainfile.php was written to directly. Nothing is copied that I know of.

The only thing I did to mainfile.php prior to installation was:

1. copy the protector version mainfile.dist.php into the www directory
2. delete the mainfile.php file
3 rename the mainfile.dist.php file to mainfile.php

Other than that (which the instructions tell me to do), everything else is stone stock shipped distribution.

Any help would be appreciated. I've got my personal site down because of this, and I'm not upgrading any of my client's sites until I know what this is.

By the way, The upgrade procedure this time out needs work badly. We had a nice simple upgrade path in the past, by downloading the upgrade you needed, copying the files, and running it.

It's difficult to figure out now for newbies (and guys with senior moments like me).

Please HELP! This is a NEW install for all intents and purposes, and it's just NOT working.

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/7/16 14:08
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#15

Re: Block and Module "Weight" Values

Quote:

GPboarder wrote:
Setting the weight of a block is like giving it a density. The more dense things sink to the bottom and the less dense ones float to the top. 0 in the blocks weight is the equivalent of saying that there is nothing pulling it down so therefore it will compete for the top location with other blocks having a weight of 0.

I just tested 10000 as a weight with no problems but can't tell you an actual limit.

There is a specific setting in the Blocks Administration area that determines if a block is visible or not. The weight does not affect the visibility.


Thanks! I like your density analogy. I'll use it in my article if you don't mind. I'm trying to really explain this in a way a XOOPS Newbie will get it.

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/7/16 14:05
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#16

Re: Block and Module "Weight" Values

Quote:

Bandit-X wrote:
1. smallint(5) unsigned (Not Zero Fill), range: 0 - 65535

2. smallint(3) unsigned (Not Zero Fill), range: 0 - 65535

3. setting blocks to 0 weight makes it appear closer to the top. if two or more are zero, then the one with the lower blockid will appear closer to the top. the greater the number, the block will appear closer the to bottom, compared to other blocks.

==
note. smallint(5) and smallint(3) I don't know if it is phpmyadmin or what but since it is unsigned, they are just smallint. also the input for the text boxes have a limit on 5 characters that was coded.


Thanks, that's exactly what I needed. I'm developing a module to select the blocks you want from a given section, and alphabetize them, in up or down order, or move them around a little easier. I'm also planning on having the modules move up and down the menu in the same way. I'm using weight as the simple way to do that.

In the interim, I thought I would just write up how it all works so that folks who are new to XOOPS can read up on it. The documentation so far leaves a lot to be desired on this one particular section.

This will be the first (of many I hope) articles on my new XOOPSTyro.com web site that I'm still developing.

As always, the community steps up! Thanks!

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/7/15 15:24
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#17

Block and Module "Weight" Values

I'm writing an article for my web site, and I need a little info that I can't find after searching the XO site pretty thouroughly. Knowing that some of you out there know the site a lot better than I, I thought I would pose the questions here.

1. What is (are) the minimum and maximum numeric values that can be put into the weight field in blocks configuration?
2. What is (are) the minimum and maximum numeric values that can be placed into the module weight field in module configuration?
3. In modules setting a value of 0 will cause the module to not be visible in the menu. Will setting a value of 0 in a block have any effect?

Thanks in advance for any help. I'm developing an admin module system to easily order blocks and menus, and an article to go along with it.

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/1/21 22:08
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#18

Re: Huh.... Then.. start!

From a commercial standpoint, there are now two pretty good books on Xoops... (from Amazon.com):


Building websites with Xoops: A step-by-step tutorial

Building websites with Xoops: A step-by-step tutorial by Steve Atwal (Paperback - Oct 31, 2006)
Buy new: $29.99 32 Used & new from $29.00
Get it by Tuesday, Jan 22 if you order in the next 54 minutes and choose one-day shipping.
Eligible for FREE Super Saver Shipping.
3.0 out of 5 stars (4)
Books: See all 126 items
2.
XOOPS - To Create Dynamic Web Sites Simply

XOOPS - To Create Dynamic Web Sites Simply by Stefano Silvestrini (Paperback - Nov 19, 2007)
Buy new: $14.95 $10.17 5 Used & new from $9.35
In Stock
Eligible for FREE Super Saver Shipping.
Books: See all 126 items

The Italian Version:

XOOPS creare siti dinamici con facilità

XOOPS creare siti dinamici con facilità by Stefano Silvestrini (Paperback - Jun 1, 2007)
Buy new: $14.95 $11.66 27 Used & new from $8.86
In Stock
Eligible for FREE Super Saver Shipping.

So if you have some pocket money, and want a nice "keeper" manual, these aren't bad. They all get a little dated trying to keep up with versions, but in general they are pretty acurate.

Hope this helps...

Byron
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/1/21 21:41
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#19

Re: Xoops Modules (All Xoops Users Please Read)

First off John, let me say a hearty "Well Done" for stepping forward with what will surely be a "daunting" task. The module repository is frustrating at best in it's present incarnation. The categories make little sense. Most modules have little or no documentation. The ones that do work are lost in the rubble of the ones that don't. You are dead on in all counts.

Quote:

jlm69 wrote:
I am not a XOOPS Core Developer, nor am I part of any team in Xoops. I am just a XOOPS User just like you, and I like XOOPS alot.


That's the best kind of motivated user. Some of the "Core Team" could learn from you! I like XOOPS a lot too. I'll pitch in where I can. I have a hard drive that is essentially a collection of all things Xoops. It's not sorted to any great extent, and it's certainly not ready for prime time, but I can build a torrent, and you or anyone else can get it (it's a BIG file). I spent 5 years collecting all of it. I'll leave it up to the new Module Dev Team to sort them all out. I can help some, but I haven't even scratched the surface on the vast majority of them.

Quote:
Over the years I have read some posts saying that this module or that module doesn't work anymore. I think we should get this sorted out.


I couldn't agree more!

Quote:
BlueStocking has posted a zip file with all of the XOOPS Modules in it.


And a hearty big thanks to Darcy for doing that too! I downloaded it the day it went up to compare against my list, and I have a LOT more than the zip file, but there were some new ones in there that I didn't have.

Quote:
I think We as Users of these modules should help these good people I mentioned earlier because they can't do what I am thinking by themselves, so here is my idea.

When you download a module to use on your site and it doesn't work, don't just be disappointed and walk away from it, you can notify me or we could have a special forum to report 'Dead Modules', some way of knowing they don't work. Then we can have them removed from the Module Repository and maybe have a special place for these 'Dead Modules', once they are listed maybe someone who wants to use one of them and has the ability can update it so it can be put in the Module Repository again. To make this work we would need people willing to do the testing of these modules, no one person or small group would be able to do this themselves, but as a community we could make this happen.


How about another field in the WF-Downloads or whatever it is that XO uses that contains the "status" of the module. Like "Certified" for modules which have been tested and found to be working by the Module Dev Team, "Pending" for a module that is working with the current version by popular report, but which has not been tested by the Module Dev Team, "Broken" for modules which do not work, and "Obsolete" or "Superseded" for modules that might work, but newer versions exist? I have long maintained that the modules for file upload and download are inferior to the very oldest BBS software's capabilities back in the 80's and 90's.

Module documentation standards MUST be imposed. Additon of a fileid.diz file to describe what the module does... a Readme with special instructions... install_en.txt for a file in english that describes installation... manual_en.txt for the operations and admin manual... user_manual_en.txt for the user operating manual (yes, the users need to know all those fancy features built into the module, or what point is there to the module?)... and so on... I have lots of ideas... maybe we should open a section on the Wiki for a module "Submission Standards" compliance rule set??


Quote:
I'm not asking you to test all the modules on the list, but pick the one or more that you would want to use.
If you would like to contribute something to Xoops, but don't feel you can, here's you chance.

We could even have polls or some way of knowing which modules are most important to the XOOPS User (You) and then maybe some developers would see the need and fix a module for the community.


I have to disagree with you here. How many times have you seen "I can't get module ___Fill_in_the_Blank___ to work ... blah blah blah..." and in the next 4 posts they go something like "works fine here", "no problem", "how do you (unrelated to the module problem to begin with) do something". All of these are mis-leading to the newbie, and the pro. The fact is that some of us can't read, and we miss the detail that makes the module work, causing us incorrectly to believe that it doesn't. Do we want the status of a module to be determined by the "mob" as someone once put it?

I believe, and have always believed that a module when submitted must be tested by the "Module Dev Team" (for lack of a better term for who does the testing), and goes into one of those states I mentioned above until it's tested. Yes, that's a lot of work NOW, because there are some 2500 modules, and 3000 themes to be tested over the life of Xoops. But over time, as things get tested and certified, the actual number of modules to be tested per month is manageable for a team of three or four people dedicating an hour a week to Xoops. I believe it could be done, and it's the RIGHT way to do it. Otherwise, it's chaos, and a year after you finish, we'll be right back where we started... if we finish!

Quote:
That's kind of how I got started doing my modules, I wanted a Jobs module for a site, so I made one out of the myads module, then I saw that other Xoopers wanted a Jobs Module so I released it, and as they say the rest is history.

I don't have all the details figured out it's just an idea right now , but lets figure a way to make this or something like this happen. I know that the XOOPS Core Developers and the XOOPS teams out there read these posts, and I'm sure they wouldn't mind a community effort like this, in fact I don't know, but I think they would really appreciate it.
I have not asked for permission from anyone to do this and no one has asked me, it is just me asking the Community I have been a part of for a long time to come together and help those good people make XOOPS the best it can be.


Let me add, that there is a bigger XOOPS Community... Cube, Tube, ImpressCMS, you name it, there are forks. If we really want to take the "higher ground", another field in the module repository might be whether the module is compatible with any of the other forks. We don't have to test them, we just have to have the submitter/author tell us that it works with XOOPS Cube, and XOOPS Classic... just a thought, and I know that it would go a long way towards getting some great modules that the forks are developing into our repository, and getting the entire community including the forks working together. Just a thought.


Quote:
If it takes having a special site for these Dead Modules, I could make it. I am willing and able to work on this. How about You.

This is not for Modules that have a few errors, it is for Modules that no longer work at all.


If they don't work with current versions, or don't have support any more, why keep them? Make a list certainly, but I wouldn't try to maintin the dead modules in the repository other than as mentioned somewhere else, having a "catchall" area on Sourceforge or somewhere. BTW, Sourceforge is in trouble. The advertising is going up because their funding is going down. The thingy asking you to register on every download is NOT going away. And it's getting VERY slow. There are about 20 fewer mirrors than there were this time last year. I'd rather see a XoopsForge set up somewhere for module development, and a simple FTP site for old and dead modules.

Quote:
Thanks for listening and if you have any ideas please don't be shy.


John Mordo


I'm not! It's a great idea. Let me know how I can help, and if you want all the stuff I have, drop me a private mail... and before anyone else goes running for the PM button,... I'm offering this to the Module Team, NOT the general population. Maybe I'll put the torrent on a public tracker somewhere (any offers for who would like to host it?), and if someone offers about 4.3GB of space (unzipped) to hold it, then we can make it publically available. I can't spend the time tidiying it up, but at least you'll have a LARGE collection to get into... Volunteer sites that run BT?

Let me know what to do and I'll help when I can.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------


wingrider101

Not too shy to talk
Posted on: 2008/1/13 15:34
wingrider101
wingrider101 (Show more)
Not too shy to talk
Posts: 101
Since: 2004/5/26
#20

Re: A proper project management module?

Quote:

InnoSense wrote:
Hello, Byron.

In two days i will write a short report about XOOPS <-> EGW.


Sorry for outdated reply.

Good luck!



I look forward to your announcement. I tried "dotProject", but it had a lot of bugs, and was difficult to use.

BAM
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Byron McKay
wingrider101 at gmail dot com
http://byron.homelinux.com
http://www.xoopstyro.com
-------------------------------------
Xoops CMS Intranet sites for Business
-------------------------------------



TopTop
« 1 (2) 3 4 5 6 »