Import problems
| Project: | Import HTML |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm very impressed with this program but since I cannot precisely do what I set out to do with it yet, I thought I should let you know by way of a couple of examples.
Attempted to import this page:
http://drupal.holidayjunction.com/ihs/out/hotels/ca-on-ottawa.html
and also for example this page:
http://drupal.holidayjunction.com/ihs/out/hotelinfo/71982.html
The results were:
http://drupal.holidayjunction.com/hotels/hotels/ca-on-ottawa.html
and
http://drupal.holidayjunction.com/hotels/hotelinfo/71982
respectively.
There are a number of comments in the source code where apparently the software admits it hit a bump and decided to do nothing.
Here is a list of things that I see that are not imported correctly:
in http://drupal.holidayjunction.com/hotels/hotels/ca-on-ottawa.html
1. there is an or some other reason for a line across the middle of each hotel's description which does not appear in the original.
2. The red colour of the rates information is lost.
3. The blue box around the get rates information is lost
4. The arrival date drop-down is lost
5. The get rates link does not work.
With the individual hotel listing example
http://drupal.holidayjunction.com/hotels/hotelinfo/71982
points 2 to 5 also apply.
Thanks in advance for anything you can do.
...Rob
rhuntley@holidayjunction.com
#1
Heh.
That's mostly "by design".
PLEASE get firebug and look at the resulting HTML.
The line is coming from Drupals system.css - indicating the top of a table. Override it as usual in your own css.
Your old colors were part of the old theme and css. Your new theme does not have that "hotelRates" style so it's not coloring it in. Add something equivalent to your theme and it will.
Forms are not supported - there is no way that we can predict or replicate the functionality you've put behind form submissions! You have the individual data pages, but are expected to use other drupal modules to add those interactive features. Saving a form as HTML content in the node body is a terrible idea. You should probably strip those embedded forms out entirely.
If you look at the import result you will see the words:
<!--Form element discarded on import. It will need special attention-->It may be possible to continue using your old form handler, with some careful work, but that is not predictable or automatable.
You appear to be using import_html to import listing pages as well as individual content pages. That's not going to work well. You should import just the content pages (each individual hotel) then re-construct the listing pages using Drupal tools like taxonomy or views that will display the teaser views of the hotel details.
You probably want to try importing with the table-stripper function on. Most of those tables look like just layout - the one that isn't is a the form which should be dealt with differently.
#2
Thanks very much for taking the time to analyze my situation. I'll approach a programmer to help me with this. I'm sure your analysis will help.
The hotel network that supplies the page generator that I am hoping to adapt to a drupal-based website actually offers 3 templates for the pages. One is html and 2 are CSS. Since I have only html background, and since I needed to edit out some of the non-required headers and footers, I chose to use the html template. Perhaps one of the CSS templates might be more appropriate if I get a programmer to help in making my edits.
...Rob
#3