Import

There are lots of sites on the web, just do a search. You will have to format them correctly to import.

I'm using D6.2 with the 1.1a2 version of Quotes. I'm entering this as a documentation note so that maybe FAQ or usage info docs can get an update.
- Going to the 'mass import' option changes the URL to node/add/quotes/import, but only re-displays the standard single-entry form.
- I hope this isn't stupid but if the quote text itself is a required field and we want to import file, where do we enter the file name, and how do we do that without entering a quote? I haven't checked the code, but are we expecting a different form? I tried entering a filename in the text area with no joy.
- What is the format of any path entered to a file?
- Is the file specified as an attachment? (I don't think so, gotta ask.)
- There are so many "fortune file formats" out there including packaged RPMs, text files with a corresponding .dat. Can you provide some guidance as to what the specific format is that we should be looking for to import collections of quotes?
- Linux systems use ./games/fortune files. Are those what we need?
- Some files call motd files 'fortune' files, but the format isn't the same as others.

Any simple answer(s) would be appreciated. Thanks for a response and for the effort on this module!!!

This should have been a new issue. If you see an issue that's in a closed status ('closed," "by design," "duplicate," or "won't fix") it is better to open a new issue, possibly referencing the closed one if it is similar. Changing the version or component is another tip-off that it should be a new issue. This all helps others do better existing issue searches.

The 6.x version is in alpha status because it's not perfect yet. It was primarily created for those who were migrating from 5.x and needed it. I was hoping for more comments like "In 5.x there was a thing titled 'Notes on Importing' but it seems to be gone."

I think bring those notes back will take care of many of your questions. Meanwhile, the best source of answers is the documentation (link on the project page). I certainly welcome other suggestions on how to improve the form and it's descriptive text.

The "mass import" link needs to go away, as the function is no longer separate in the 6.x version due to the menu changes in Drupal 6. This function will also be changing again soon as I have found what I think is a better way to do it. There is an issue open to track that change.

Importing a file has never been an option with Quotes. One uses copy-and-paste to put the quotes in the body field and the import parser splits it into individual quotes and creates nodes for each one. There was a request to do a file import but it would require major changes to the code structure and would likely encourage you to import so many that you would end up running out of execution time and breaking your site. I may look again at doing this some time in the future (similar to the way Search can break the indexing up into better chunks). But don't hold your breath.

Nancy - all understood, thanks. It was only after I posted my inquiry here that I saw your presence in the other parts of this project and recognized the true state of the project. Having just found the module and made the decision to just start working with Drupal as of v6 I don't have the perspective of some of the v5 history here.

So - given all things in the air with your current effort on this, the alpha status, and some lack of documentation - what would you recommend at this point? I would be happy to help test your alpha cuts in v6 and contribute toward the effort but I'm not sure how to contribute if you're actively making structural changes. I have 30 years of development experience but I'm still getting familiar with PHP and can't contribute too much in that regard. (Isn't that always the story?) I'll update docs as I see new revisions and come to understand how it's supposed to work. Is the best approach for right now to just hang tight until you've nailed it down a little more toward a beta? Thanks again.

There shouldn't be a big deal about using Quotes in 6.x. I wasn't happy about the state of the import conversion and posted in the forums looking for a better solution; one was offered. As long as any users of the module understand that it will probably change (but only the import function), then it is reasonably safe. The rest of the module is pretty much the same as the 5.x version.

In some respects, you, as a new user, have a more valuable insight than the existing users because you see where the port is lacking. Eventually, other new users will come along and you help in improving the module will make their experience better. Documentation improvements are amongst the hardest to accomplish because I know what it does and have to really think hard to decide what someone who doesn't know the module needs to see.

Believe it or not, "30 years of development experience" is probably half the battle to learning PHP. In January of 2007, I wrote my first line of PHP for my first Drupal site (oh, I also have 30 years of development experience). Now I'm maintaining 16 or so contributed modules and at least as many sites.

I just restored the help for mass importing to the module. It will be in the 6.x-1.x-dev version that will roll out around midnight GMT.