This may turn out to have been a stupid question, but here goes anyway: When you create a new subscription offer, you have to specify a subscription type or level. What is this, and how is it used?

Jere

When creating a directory like a business directory or classified ads, you need a LOT of categories, and it would be nice to have a way to create the entire cat/subcat structure at once. Rather than build it into efqDir, though, instructions to create an sql file with Notepad or something similar and then import it would be sufficient. I did this once with mxDir, and it saved a ton of time. Can this be done with efqDir, also?

Jere

Okay, I'm finally able to play around with it a little more. This time Version 1.0 Final. I'm just going to observe or ask as I come to things:

The extreme flexibility of this module creates issues which wouldn't exist otherwise. For example, since you can create multiple different directories, you can do things like have a business directory and a separate classifieds directory. It seems to me that, in a scenario such as this, it might be confusing to mix subscription types for different directories like these.

I would personally prefer to have separate subscription types for each directory, but I realize, also, that you can't implement everything that the flexibility of efqDir makes desirable. An acceptable, and perhaps easier, alternative would be to make efqDir clonable or to just publish cloning instructions.

I'm really looking forward to the evolution of efqDir.

Jere

Quote:

It was chmod-ed to 444, and it was overwritten. In FTP-ing the files up, you have to grant permission to replace the files. You can do it all or one at time, which would be impractical. Doesn't a chmod-ed 444 file get replaced, too?

Jere

Just this one:

The upgrade instructions in the Upgrade directory are wrong.

Quote:

These instructions do not tell you to delete mainfile.php and the Install folder from htdocs before uploading. That's a disaster waiting to happen. Correct instructions are in release_notes.txt.

You shouldn't have to look for the right instructions, and they certainly should be in the Upgrade folder. That's the first place anyone would look. And, IMHO, the instructions should be in a file named "upgrade.txt".

Jere

I don't know if life4me2 still is or not, but I still am. I've been waiting on 3.01 final but decided to go ahead and try RC1 and am having problems. I'm using XOOPS 2.0.16 and PHP 5. Please advise as to what to do.

Also, how is mxDir development going? Still perking?

Jere

I posted a request for help in the Installation Troubleshooting forum, but I guess that was the wrong place, since I got no replies. Since then, however, I've learned what screwed up and am trying to fix it, but I still need some help.

In the readme.txt file of the Upgrade directory for this version, it says:

Quote:

Now this is not correct, is it? I mean, it is supposed to say to delete mainfile.php and the Install directory from the htdocs directory before uploading. Otherwise, you will overwrite your existing mainfile.php and crap out your existing installation, correct?

This is a test site, and I didn't back it up. Still, if I can avoid having to reinstall, that's what I would like to do. Anyway, going through this is helping me to learn more about Xoops, so I don't consider it time wasted. If this had been a production site, I would have backed it up, but I would still be disappointed at the erroneous instructions.

Anyway, I overwrote mainfile.php. I figured I could replace it with the same file from another 2.0.16 site and tweak it with proper info, which I did. Then I deleted the install folder and entered the address to upgrade/index.php in my browser. This time I got the upgrade choices page, but it thinks my installation is a 2.0.13 one. Here's what it says:


upd-2.0.13-to-2.0.14 Yes
upd-2.0.15-to-2.0.16 No
upd-2.0.16-to-2.0.17 No
Proceed to upgrade

So, why did this happen?

Where's the URL?

Anybody?

Did I screw this up somehow, or does this upgrade not work?