Menu

4.2.3 Autocomplete oddity

Help
Victor H.
2010-04-17
2013-05-30
  • Victor H.

    Victor H. - 2010-04-17

    I'm a big fan of the autocomplete feature in the "Places" box - many thanks for that, whoever added it - but there's something odd happening since I updated to version 4.2.3. Let's say I'm typing in the placename for Walton County, Georgia, USA. In 4.2.1, I would type up through say "Walto" and pause for the autocomplete to suggest "Walton County, Georgia, USA". I only have one placename that begins Walto and that is it. But now, in 4.2.3, I get a list like this:

    Walto  (my entry) - which after a slight pause gives a list like this:

    Georgia, USA
    USA
    Walton County, Georgia, USA

    Anyone have an idea on why I'm seeing this, and how I might correct it? It's just a small thing but I use it all the time.

    Thanks,
    Victor

     
  • Greg Roach

    Greg Roach - 2010-04-18

    That behaviour was a consequence of a fix for finding places whose names contain accented letters.

    IIRC, it was fixed in SVN

     
  • Victor H.

    Victor H. - 2010-04-18

    Thanks Greg, I found it, and I found Wim's original bug report (thanks Wimniny) of 1 Feb. I see that in SVN some of autocomplete.php has been moved to functions_db.php, so … I'll await the next release.

     
  • Stephen Arnold

    Stephen Arnold - 2010-04-18

    Victor
    It may be sometime before an official release. With your experience level, why not just DL the SVN as a tarball and use it for your upgrade? Its no different than a standard upgrade, there are lots of minor bug fixes included and it is quite stable (that's what I use).
    -Stephen

     
  • Victor H.

    Victor H. - 2010-04-18

    I'll give that some thought, Stephen. I was actually looking at rolling back autocomplete.php to an older version if I could diff the two versions and conclude there was no harm. Then I looked at moving forward with functions_db.php, and ultimately concluded that this particular annoyance is not worth the trouble. It would actually be easier just to pull in the whole SVN as you suggest, not as a true SVN but as a one-time package. I'm still reeling from the Lunarpages fiasco, and while my instinct is to take baby steps with code changes, it might perhaps be better to take the leap to move up to the edge here. Thanks for the input.

     
  • Victor H.

    Victor H. - 2010-04-18

    I took the plunge to load in the SVN tarball (trunk only) and I am getting the same "undefined index pedigree_map" that was reported here https://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/3506065 and also on Nigel's patch item. Tracing my way up the SVN chain for includes/classes/class_menubar.php from where this was fixed on 6669, I saw Greg's note about new database tables. Do I need to reimport my gedcoms to populate these new tables?

     
  • Stephen Arnold

    Stephen Arnold - 2010-04-18

    Not sure, but it never hurts. With the size of mine, even on a fast machine, I hate to do so, but from time to time do so anyway.
    Greg would better know this than I.
    Stephen

     
  • Victor H.

    Victor H. - 2010-04-18

    Picture a crazyeyes smiley. After messing with things for a while, the pedigree_map index errors cleared by themselves. Perhaps it was a cache problem. At the same time that cleared, I lost my Journal items, so it does sound like cache. Now to find out how to get those journal items back. :-)  Not a big fan of those silhouettes, so I renamed them and copied pixel.gif into their old filenames. And I'm off to explore more of the goodies.

     
  • Greg Roach

    Greg Roach - 2010-04-18

    <<Greg's note about new database tables. Do I need to reimport my gedcoms to populate these new tables? >>

    No need, if going from 4.2.3 to latest svn.

    <<Not a big fan of those silhouettes, so I renamed them and copied pixel.gif into their old filenames.>>

    Or you could have used the config option "show silhouette images yes/no"

     
  • Victor H.

    Victor H. - 2010-04-18

    <<Or you could have used the config option "show silhouette images yes/no">>

    :-D  Awesome. Done. 

     
  • Stephen Arnold

    Stephen Arnold - 2010-04-18

    Victor
    Glad I 'twisted' your arm, as the current SVN release truly is 'awesome', with the fixes and features.
    BTW, I found the page display and charts much more balanced with the silhouettes as I have many photos, but as you discovered, that's a personal configuration, as are many features.
    -Stephen

     
  • Victor H.

    Victor H. - 2010-04-19

    Appreciate that, Stephen. Lots of coffee and a good steady rain outside made it a good day to take that leap. Running from SVN might be an option for me at some point when I have more trust in my host and in my own understanding of SVN.

    Apologies for dragging this thread on for a bit longer, but since I had the tiff with Lunarpages and moved up to 4.2.3 and now to the latest SVN snapshot, I'm having a problem with media. I'm using the old-school media rather than the Lightbox solution. The new media is being uploaded to the right places, but when I open the media viewer there is the indication of a broken image link there. The thumbnails work fine. Here is how I have it set up in the Gedcom configuration file:

    Multimedia directory = media/    
    Media Firewall = Yes
    Media Firewall Root Directory = ../../vmedia/

    So I have a  directory, and it's the thumbs subdirectory there where the thumbs are created and stored, and I have a  directory outside of publicly addressable space, and that is where the original media is stored. The media viewer is not now finding that protected directory to display the original media. I would appreciate any clues on this. I think the problem is simple and I'm just not seeing it.

     
  • Stephen Arnold

    Stephen Arnold - 2010-04-19

    Victor
    Probably a .htaccess issue with the changed folders and new install. Simply turn off media firewall, be sure to have the MFW directory at full R/W permissions (same for /media where you store the thumbs). I prefer restarting the browser, reentering PGV and then switching it back on, letting it move the files back to protected MFW directory. Don't forget to clear your caches, then all should be OK.
    Stephen

     
  • Victor H.

    Victor H. - 2010-04-19

    Indeed it was the .htaccess issue. Turning MFW 'off' and save, then 'on' and save did the trick. Perfect! Thanks for all your help today, Stephen.

     

Log in to post a comment.