Image Host Grabber

[effCup]

Pale Moon, Waterfox...

[ConstantOgler]

Could one of you code warriors please explain to non-tech how you use the code /script above to improve or fix IHG? Must one be coder to do it? Also what is kind or scope of problem this can solve?
For me IHG is compatible w ff 54.01, generally works OK on Ibam & Imven. But it does not work on p&h, pixhost, or other sites which have no gallery navigation. Is that a coincidence?

[effCup]

Originally Posted by ConstantOgler

Could one of you code warriors please explain to non-tech how you use the code /script above to improve or fix IHG?

IHG is not "broken". If/when host sites change their systems/configurations, IHG solutions/approaches may need suitable amending. Changes to browsers (e.g. FF & it's support/not for such plug-ins/add-ons) may also cause failure.

To amend, go to your browser menu for: tools -> ImageHost Grabber -> Host File Editor (that is, unless you or your browser has placed IHG somewhere else).

Find the entry for the host you want to edit/amend. If not there already then it's easy enough to make a new entry (don't simply over-write/save over an old one).

Paste in the relevant pieces for that host--e.g. some of those posted above in this thread. Save changes. Test.

Originally Posted by ConstantOgler

Must one be coder to do it?

It's largely copy & paste. I wouldn't class that as "coder".

You can try writing your own solutions if you know a little regular expressions syntax. There's an old pdf guide on the IHG website, plus various other resources on regex on the web, etc. But start with copy & paste?

Originally Posted by ConstantOgler

Also what is kind or scope of problem this can solve?

The potential scope is pretty limitless. That's kind of a piece-of-string-type question.

An example practical scope is: I can use IHG to batch-download full-size images hosted on, for example, P&H servers. I don't need to access the images manually in my browser and save them individually.

Another kind of scope: these "patches"/"solutions" will only last until IHG next updates its host file server. Hopefully their updates will incorporate any such (or better) improvements, but there's no guarantee of that. That's why it's wise to keep a copy of any amendments you make/use--both the "before" & "after". It's like saving your homework before the dog has a chance to eat it.

Originally Posted by ConstantOgler

For me IHG is compatible w ff 54.01, generally works OK on Ibam & Imven. But it does not work on p&h, pixhost, or other sites which have no gallery navigation. Is that a coincidence?

It's a coincidence.

There are proposed solutions to some of those sites already posted above in this thread. They work regardless of the host site's support/not for gallery navigation. I'm not aware of any IHG solutions that do use that, & can't imagine that they ever would need to, but I haven't looked at every last one & there are quite a few.

[buttsie]

Originally Posted by fmebree

so now i am told that imagehost grabber is not compatible with the newest version of firefox???

any ideas

Like effcup said choose another browser

On ghacks its mentioned current add-ons by version 57 (14/11/2017)
will either change to become a webextension or they will be dead.

As the IHG developer has already gone over to Pale moon .org
ihg on firefox will be dead



IHG is the tip of the iceberg with add-ons
- currently only 3,617 add-ons are compatible with FF57
Context - 16% of all add-ons are compatible with Firefox 57 at this point in time.

- down them all - wont be continuing on firefox

Firefox Add-ons WebExtensions State July 2017
By Martin Brinkmann on July 7, 2017 in Firefox - Last Update:July 7, 2017

Mozilla plans to release Firefox 57 as a WebExtensions supporting browser only in regards to add-ons. This means that any add-on that is not a WebExtension by that time will stop working. Firefox 57 will be released on November 14, 2017 according to the schedule of Firefox releases.

https://www.ghacks.net/2017/07/07/fi...ate-july-2017/

The only reprieve - extra time

Note: While Firefox 57 is the target, the change may be postponed by Mozilla, for instance to hit the browser after the next major ESR release in March 2018.

[effCup]

With imgbox, until recently I've successfully been using the following:

Host Label: imgbox
URL Pattern: http:\/\/imgbox\.com\/\w+
Search Pattern:

"REPLACE: '(http:\/\/)(imgbox\.com\/\w+)', '$1i.$2'"

----

There seem to have been some slight changes made to that host, see e.g. here.

Host Label: imgbox
URL Pattern: http:\/\/imgbox\.com\/\w+
Search Pattern:

function(pageData, pageUrl) {
	var iUrl = pageData.match(/src=('|")(https?:\/\/images\.imgbox\.com\/.+?)\1 title=('|")(.+?)\3/);
	return iUrl ? {imgUrl:  iUrl[2], fileName: iUrl[4], status: "OK"} : {imgUrl: null, status: "ABORT"}
}

----

The above has not been widely tested so please let me know, preferably here, if you strike any issues with it. If reporting problems please remember to include a link to some example(s) to demonstrate the issue.

Just thought: I also haven't checked whether all imgbox images have been moved to that newer storage format, or whether some are still stored in the "old"/"legacy" format. Again let me know.

[gnewellperv]

^^ Thanks very much for the search pattern code update, effCup. I only hit the problem about three days ago and that's worked for me.

My previously paralysed IHG is now flowing with imgbox images again.

[effCup]

Originally Posted by effCup

whether all imgbox images have been moved to that newer storage format, or whether some are still stored in the "old"/"legacy" format.

Thanks to haVEFun here for pointing out some examples where a variation upon the legacy storage format still applies, e.g. here, here, here.

The following's hardly elegant, but.

Host Label: imgbox
URL Pattern: http:\/\/imgbox\.com\/\w+
Search Pattern:

function(pageData, pageUrl) {
	var iUrl = pageData.match(/src=('|")(https?:\/\/)(i|images)(\.imgbox\.com\/.+?)\1 title=('|")(.+?)\5/);
	return iUrl ? {imgUrl:  iUrl[2] + iUrl[3] + iUrl[4], fileName: iUrl[6], status: "OK"} : {imgUrl: null, status: "ABORT"}
}

[solarbear]

That got my imgbox downing revived, mucho gratitude..


EDIT: the old search pattern script worked begrudgingly for cuzzymans posts, the new script killed the 09-06-17 cuzzyman post that i saw, but the new script definitely revived ludde67 posts from 09-09-17 onward. so maybe the old script is good for imgbox until that 09-06 date range, the new script afterward.

[effCup]

Originally Posted by solarbear

the old search pattern script worked begrudgingly for cuzzymans posts, the new script killed the 09-06-17 cuzzyman post that i saw
so maybe the old script is good for imgbox until that 09-06 date range, the new script afterward.

Huh? What? Please post links to some example post(s) of any problems so I can try to follow your meaning? Your only link was to a poster, which is not as helpful. Ta.

[solarbear]

ok
this page , imgbox old search pattern was working, , but the new search pattern isn't getting through

http://vintage-erotica-forum.com/t95...llatio-bj.html

I will check the newer imgbox postings from september 9th forward, as that was when the ludde67 posts started and the new search pattern connected to them whereas the old one was denied

ok, this page , the new search pattern is working from september 10 onward with multiple imgbox posters

http://vintage-erotica-forum.com/t20...-redheads.html

and this page has older imgbox posts, which didn't connect with the new search pattern script

http://vintage-erotica-forum.com/t20...-redheads.html