Missing Image Utility/Scanner [Support Thread]

[Graniteman22]

Were all if the files uploaded to the proper location in your admin directory? Including th SQL patch?

I deleted the 1.0.3 version and downloaded your 1.0.2 version. The download only included one php file to move onto server.

[retched]

I deleted the 1.0.3 version and downloaded your 1.0.2 version. The download only included one php file to move onto server.

With 1.0.2 (my version), all you have to do is upload it to the server where ZenCart is (preferably the main directory). Edit that one file so it is pointing to the /includes/configure.php file. (Either the one in your admin/includes or your /catalog/includes is fine.) Then call the file in your web browser directory. When it's done and you are satisfied with your results, remove it from your server.

Like I said, I'll figure out what happened with 1.0.3 and what it's supposed to do. But there is already a version on the GitHub (2.0.0) which is going to the ZenCart backend. That one is NOT ready as of yet and will likely not end up using the code provided by express1973. But we'll see.

[explorer1979]

Hi Graniteman22,

You need run the SQL Patch if you are using ZC 1.5.3, and copy all the files on 1.0.3 to your folder,
But rename the path as your admin folder

For example, if you rename your /admin to /admin123

Then you must copy all the zc_1.5.x/
file to under your /admin123 folder.

then login to your back end, then Tool --> Install SQL Patches
then open /zc_1.5.x/install_sql.sql
Copy this SQL coding, then paste in Tool --> Install SQL Patches

INSERT INTO admin_pages (page_key, language_key, main_page, page_params, menu_key, display_on_menu, sort_order) VALUES ('missingImagesChecker', 'BOX_TOOLS_MISSINGIMAGESCHECKER', 'FILENAME_MISSINGIMAGESCHECKER', '', 'tools', 'Y', 50); 

Then reload your admin page, then you will see the new Menu Under Tools --> Missing Images Checker

Thank you

Best Regards,
Jimmy Chan
http://www.jimmychan.tk
http://explorerhome.no-ip.org/blog

[explorer1979]

Graniteman22

If your shop /admin is rename to something like that /admin123, then below is what you do

Copy
/zc_1.5.x/admin/missing_images.php
to
/admin123/missing_images.php

Copy
/zc_1.5.x/admin/includes/extra_datafiles/missing_images.php
to
/admin123/includes/extra_datafiles/missing_images.php

Then on Admin Back End, go Tools --> Install SQL Patches

INSERT INTO admin_pages (page_key, language_key, main_page, page_params, menu_key, display_on_menu, sort_order) VALUES ('missingImagesChecker', 'BOX_TOOLS_MISSINGIMAGESCHECKER', 'FILENAME_MISSINGIMAGESCHECKER', '', 'tools', 'Y', 50); 

Then reload your admin page, then you will see the new Menu Under Tools --> Missing Images Checker

Hope this help.

Thank you

Best Regards,
Jimmy Chan
http://www.jimmychan.tk
http://explorerhome.no-ip.org/blog

[DigiBooks]

Hi

I just downloaded the latest version of the Missing Image Scanner (oddly enough when it is installed and run it says version 1.02 and not 1.03 - but if I try to access it direct;y from the browser bar then it does force a login so I guess the version should just read 1.03?)

The main problem I'm finding is that it says all my products (on the test site) have an image - but they don't. If an image is uploaded (and therefore stored in the product) and then subsequently deleted then the plugin will detect that:

Odd Thomas /home/sites/digibooks.org.uk/public_html/2014ZCtest/images/oddthomas.jpg Image file does not exist. Edit the product's details and click "delete image" to remove from database.

If however, an image was never upoaded, then the plugin says everything is fine:

Alex Cross /home/sites/digibooks.org.uk/public_html/2014ZCtest/images/ OK

Is there a way to adapt this please so that it does not just treat the images directory as being an image?

Thanks

[explorer1979]

DigiBook,

My 1.0.3 version just add the coding for the FORCE LOGIN first by Adminb before can using this of the Core Files, plus Menu only.

Other coding are 100% same as the original 1.0.2. It is why when you are using it, still see the version number is 1.0.2 not the 1.0.3.

So if 1.0.2 function or bugs, my 1.0.3 will be same as the 1.0.2 too.

Hope the original module author can fix this on future version.