XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


(1) 2 3 »


1
zaphmann
Re: morphogenesis 2.0 to start with or previous version?

  • 2007/6/13 21:55

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Not getting any help or advice on this has left me in limbo.

It seems a bit odd to post an effective advertisement for morphogenesis on the XOOPS main page then not answer such a basic question...
Topic | Forum


2
zaphmann
Re: Theme kills Xoops - Should Themes be avoided??

  • 2007/6/13 21:29

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Quote:

Biteronboard wrote:
Sounds to me like typical issues an inexperienced user would have with XOOPS.

Typically any folder named "res" is a resource folder...

As a theme designer, I am a bit put off by...
Quote:
Theme kills XOOPS - Should Themes be avoided??

In fact its kind of insulting...

If thousands and thousands of people have used this system successfully for over 5 years... maybe its not the car but the driver.


Hello - as I started this thread with that title i would like to apologise and stress that I do appreciate everyone's efforts and do not want to be insulting. I have since gained some more knowledge of how php code behaves in certain host environments and how conflicts between files written by the CMS (group www) clash with files ftp'd up and owned by the ftp user.

I believe that some of my template problems were in fact php fatal errors and or permissions issues. However, my post was prompted in part by another thread I found in which a full production site (of some years) was brought down by a template change.
Topic | Forum


3
zaphmann
Site wide Tags or Categories & Smart folders

  • 2007/6/4 6:23

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


OK Xoopers,

I'm in and building my site. I have various typical functional needs of a 'news' site.

I have a framework for the 1000s of pages of information I expect to enter which categorises these areas of interest. It could be news, an article, a discussion etc...

So I need 'Tags' or 'categories' or whatever word you wish to apply that hold across the whole site adding categories in separate modules is unreliable and opens up inconsistency + hinders searches.

Which leads me to searches... & smartfiles - smart like PLONE?ZOPE where you can set up a folder that has a tag associated and picks up ALL content with such a tag.

Does this exist in Xoops???

If not, what's the best cross-site tagging module??

Thanks
Zaph
Topic | Forum


4
zaphmann
morphogenesis 2.0 to start with or previous version?

  • 2007/6/4 1:29

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Having installed XOOPS & vaious modules I'm ready to select a theme and tailor it to my needs. The main XOOPS front page makes starting with morphogenesis 2.0 a must, but I can't decide. The FAQ on the subject is in french so I can't get anything from that (sadly).

I like ExNews, Blueshine & Greetea themes -
Are any of these themes I've been looking at compatible with morphogenesis 2.0 as it requires 'template' changes as well as a theme upload?

Or should I go with earlier morphogenesis release?
Is there an English FAQ? (search didn't show one)

Thanks
Zaph
Topic | Forum


5
zaphmann
Re: STUCK in a Hole! SOLVED

  • 2007/6/3 3:15

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


This problem was resolved - see posts at https://xoops.org/modules/newbb/viewtopic.php?post_id=262855&topic_id=59200&forum=1#forumpost262855

Best
Zaph
Topic | Forum


6
zaphmann
Re: Protector Install Issue SOLVED

  • 2007/6/3 3:13

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Steve et al.

I followed the advice and placed the trust path under my root and added a htaccess file per GI Joe. I had to be careful to remove Protector and undo the edits in the mainfile.php in reverse, so that I could (per instructions) set the trust path, then install Protector, then put in the include check statements...

I got the same result.

That told me that the problem had nothing to do with where it was placed.

So it made me look for the precheck & postcheck php files (they were where they should be), so as you have often been right, Steve, I rechecked the typing... and there it was - in my efforts to ensure I had the correct statement I had copied and pasted lines, somehow I had copied and pasted 'precheck/php' into BOTH includes...

I am extremely embarrassed, to compound this, because I had cut and paste I didn't of course consider the statements could be wrong... though I had looked and two others also looked, we never caught it.

So I unwound everything again, put the trust path back outside my root and it's all fine!

Thank you so much, I have green lights everywhere and am eager to proceed.

Anyone else who has protector install problems, I hope I can help them.

Thanks again
Z
Topic | Forum


7
zaphmann
Re: Protector Install Issue Narrowed Down!

  • 2007/6/3 2:24

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Hello - thanks all for the tips, I followed Stephan88's guide

Quote:
go to admin -> xoopsinfo, click "PHP Info" tab and scroll down a little to "Configuration - PHP Core". Find the "open_basedir" value and see if it is set. Is it same as your XOOPS root?


which I couldn't do last time because I couldn't install Xoopsinfo, this time it's in aandunder Server Info (no PHP Info) I found the value:Quote:
open_basedir no value no value


Does this tell you anything more than you knew already?
Topic | Forum


8
zaphmann
Re: Protector Install Issue Narrowed Down!

  • 2007/6/2 0:08

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Hello all, another days efforts and here's the update:

The statement did have a ; at the end of the line and was on one line, so that wasn't it.

I chatted with my ISP and they haven't resolved it. It seems that if the trust path is defined AT THE SAME LEVEL as the root, then it falls outside the assigned apache area for my files.

I wondered if the 'root' (Sites) should have a sublevel with my XOOPS files (equiv to htdocs and the trust path both are.

Indeed in what seems to be a documentation error this is what the Protector V 3.02 module documentation
at http://library.fishbreeder.net/xoopsdocs/protector-3-02.pdf saysQuote:
6. Edit mainfile.php, which is in your website root folder. You need to define
XOOPS_TRUST_PATH as a new constant here by adding a new line. The value should be
the physical path to the trust path folder, eg:

define('XOOPS_TRUST_PATH', '/home/my_user_account/public_html/my_trust_path');


when jus before it had said to make that same my_trust_path AT THE SAME LEVEL as public_html (see below - the actual documentation is indented)

Quote:
3. Create a new folder outside of your website root to serve as your 'trust path'. You can call
the folder anything you like, but I'll use 'my_trust_path' in this example. If your website root
is called public_html, the directory structure would probably look something like this:

/home
/my_account
/public_html [this is the website root, your site is in here somewhere]
/my_trust_path [lies outside the website root]


These statements are contradictory are they not?

Bottom line is placing a trust path OUTSIDE my root folder gives blank pages on this server Quote:
Software server Apache/1.3.33 (Darwin) PHP/5.0.4 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l mod_perl/1.29
PHP version 5.0.4
MySql version 4.1.13a


Is this unusual - surely someone should have confronted this and resolved it, or does everyone give up at this point and forget about protector?
Topic | Forum


9
zaphmann
Protector Install Issue Narrowed Down!

  • 2007/6/1 5:48

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Hello all. I have now narrowed down the protector install issue and I have Xoopsinfo to help this time too. (fyi to those who are tracking prior troubles).

This is a completely fresh install, new database, new files, everything.

Install worked after I gave an extended root path:
Previous install was going with /Volumes/XRAID01/Users//Sites - but could never see the modules installed, got path errors or blank screen (depending on the status of protector), and NO access at all through back end.

But this time I provided an extended path (same one) /Network/Servers//Volumes/XRAID01/Users//Sites

TAKE NOTE THAT THIS cleared up the module problem, and things went swimmingly (well), I was able to install and see the contents of and play around with News, Article, Backup, Xoopsinfo - in that order.

I had deliberately held 'Protector' back.

Now I carefully installed protector, setting up the files as instructed and editing in the mainfile to add XOOPS_TRUST_PATH as instructed.

That was fine and I was able to install the protector Module.

THEN I added the two lines at the end of mainfile.php. The result? As before - can't access any modules at all, just blank screens. Luckily I could page back in my browser to the Admin page, so then I commented out the added two lines with this code (which I'd added):
Quote:
include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php'


And all was fine again. So the problem lies therein. I cannot use debug or Xoopsinfo when the code in mainfile is changed, because it all goes blank.

I tried putting double quotes around it like this Quote:
include XOOPS_TRUST_PATH."/modules/protector/include/precheck.inc.php"


and that gae the same problem.

SUMMARY: I had had two problems which confused the picture. The first is solved (above) the second is isolated.

Any thoughts on this?

Many thanks
Zaph
Topic | Forum


10
zaphmann
STUCK in a Hole!

  • 2007/5/31 3:13

  • zaphmann

  • Just popping in

  • Posts: 30

  • Since: 2007/5/22


Hello Steve,

It may be a bit late for that last suggestion... Thinking that there HAD to be some problem with the minfile.php which I couldn't spot, I renamed it and put a fresh mainfile.php up to see what that would do when I selected a module (I had kept my browser open in Admin-Modules).

It gave this: Quote:
The requested URL /modules/article/admin/install/index.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


Which is quite correct the install/ step in the folder path is not there in the original unzipped module folders, nor on site...

Why was it seeking this? Does XOOPS generate it?

Anyhow, no use, so I renamed the prior mainfile.php back and OOPS!!

Now just a message saying XOOPS root path not defined no back door in either through http:///user.php this time.

I guess I really will have to start all over again?

If this is so, I have two questions?
1. I see download options for things like Commercial Pack at Source Forge - Is it OK to start with one of those?
2. There's a SQL db there on site should I have it purged first - or just use a new prefix?

Or IS there a way out of this hole? (I can't get into any admin screen or my site at all.)

Best Zaph
Topic | Forum



TopTop
(1) 2 3 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

171 user(s) are online (49 user(s) are browsing Support Forums)

Members: 0

Guests: 171

more...

Donat-O-Meter

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

Latest GitHub Commits