Simon Kane
Forum Replies Created
-
I’m sorry I am unable to explain it any clearer than I already have.
Please re-read my two prior explanation replies as to what is happening.Those files are NOT in the Media Library database.
They are ordinary files on your server’s disk.They just happen to be in the same directory as where Media Sync has been told to look.
I can not advise you as to whether they are needed or used by anything else in your WordPress installation.Please understand which direction is the “primary” for the two separate things (Media Sync plugin and Media Library component of WordPress).
Media Library looks in it’s DB and for each of the items there, it looks for a matching file. It is NOT looking at ALL files.
Media Sync’s job is to look in the specified file directory(s) and see if there is a matching DB entry for each file. It is looking at all files – even the many non-media (eg. *.css, *.log) files you have in those directories.
P.S. I note that your scan directory name is not showing up in the scan listing header – this makes me think you are running a downlevel version of Media Sync. Current is 1.2.9.
I suspect the confusion arises from the word “missing”.
Maybe it should be saying
“Show only files that do not already exist as Media Library entries.”In other words, you are seeing candidates that maybe should be imported by Media Sync —
if that’s what you want to do with them, and there are any actual files in the 3 folders I can see listed in the screenshot.They do not show up in the Media Library because there are no DB entries for them.
In other words, it appears that all is well.
If I’m reading you correctly (the confusion is “physical file on disk” or “database entry”), I think you’re asking for something that is outside of what Media Sync can do (which is add media DB entries for disk files that don’t have one).
However, the Media Library itself has two features that I think will do what you need — whether it’s Media DB entries that are not used anywhere (unattached) or media DB entries with no actual file (use the “Filter by missing file” filter). Once you have the list of what should be deleted, use “bulk delete” on it.
As always – especially when doing something like this, which could go badly – backup your database before making the changes/deletions.
You have me confused with the referenced thread’s OP, and I mentioned that I was not, and that there is no record of me BECAUSE YOU (WPDESK) DELETED IT).
Like most “modern” customer support, you maintain no continuity of any kind.
f O had done this in my nearly 50 years of technical support I would’ve been fired. In fact, I have had to discipline team members for doing exactly what your associate did.If you had NOT deleted it, you would have found that I was following on the ball YOU dropped when you gave an incomplete answer, that would cause extreme and unnecessary disruption to the OP’s – and my – site.
In short, I used YOUR plugin to create the shipping_phone field long before Woo (finally and rightfully) made it an “official” field. Then when they did this, your code blew up, and your “fix” made it worse. There is now no difference between shipping_phone and shipping_city (etc.) BUT YOUR CODE IS BLOCKING USE OF IT.
“Probably this issue is with a field added by another plugin.” Of course –
the plugin’s name is WooCommerce. Maybe you’ve heard of it.Maybe they are not following your rules of detecting a “WooComemrce Default Field”.
You might want to take that up with them.IF you had decided to split off my directly related continuation of the issue that you had rather quickly closed (1 week) WITHOUT any actual resolution (and I suspect no reply from the OP because of your first reply of “we changed stuff without warning, so you have to change stuff, even though what we changed makes it so you can’t fix it”), and an apparent lack of understanding of the actual issue (which I put a decent amount of effort into composing – and which you have thrown away), OR if you had at least mentioned that there was a fix in process, things would have gone much smoother.
But you didn’t. And I was at the current (as of that time) version (3.3). Not being a mind-reader, I didn’t know you were releasing another version – that still doesn’t fix the issue) And your fixes (3.3 or 3.4) do not mention shipping_phone at all.
And, of course, now that I installed 3.4 (fortunately only on a test system), a NEW set of problems was created ( Notice: Undefined index: class in ……/wp-content/plugins/flexible-checkout-fields/src/Settings/Option/CssOption.php on line 63), and the original issue remains – and may have even gotten worse (the metanames got changed – but after the several hours I’ve already put into this problem, I don’t remember why those fields got there — but do know that “Reset Section” doesn’t.
You get the idea why you would get zero stars if I could give it?
Your function name does not match what is in your add_action call.
Forum: Plugins
In reply to: [Disable Bloat for WordPress & WooCommerce] Disable all shop featuresAh. I was talking about server-side bloat. Ya — I can see 8MB of scripts you likely don’t need, but figuring out which is which can be difficult.
There are plugins out there for optimization, but I’m not familiar with them really.
Forum: Plugins
In reply to: [Disable Bloat for WordPress & WooCommerce] Disable all shop featuresHi!
If you don’t use something, it doesn’t need to be disabled.
Yes, that’s an oversimplification, but if you don’t have any products, they won’t appear. There is only disk-space-used (which is minimal) overhead for keeping the various pages around. Trying to delete actual code files will undoubtedly break the system unless you are an absolute god-level expert in how the woo code is organized.If there’s a cart link showing on your site, that’s a function of your theme using Woo, not of Woo ushing it on there. Yes, semantic arguments can be made, but if the theme is not calling for a “view cart” link to show, it will not show, and therefore no overhead.
There are various other things, such as links and redirects, but they can all be controlled using Woo and WP settings — but again, they are no overhead unless they actually get triggered.
Hope this helps.
Forum: Plugins
In reply to: [Media Sync] Image IDs differ after syncronizationAs erolsk8 no doubt also suspected, that’s VERY custom code doing that.
Actual WordPress work (core, plugin, and custom) is always done in PhP for various reasons.In any event, WordPress does not support post_id synchronization across sites (separate or multi-site), alsoo for various reasons – some of which you are encountering. Note also that media objects are also “posts”, along with several other things in WP and it’s various enhancements (eg. WooCommerce).
I do not know why you want/need to duplicate content across multiple sites, but I suspect this issue will only become a larger problem over time.
If it helps and is eCommerce (at least if it’s Woo), there are many supported (by plugin providers) ways to sync-up multiple online stores.
Forum: Plugins
In reply to: [Media Sync] Does it work for multisites?I’m far from an expert in multisite, but WordPress frowns upon direct DB accesses. However, I’m under the impression that each site in a MS has it’s own set of tables, and the normal DB table prefixing mechanism is what’s used.
If prefix is ‘wp’
Single_site: wp_posts
Multi_site ID=25: wp_25_posts
and almost none of the typical plugin code running around the world ever notices. 🙂The plugin author is being over-cautious in reminding people about the fact that DB changes wil occur (I asked him about his ‘caveat’ some time back. 🙂 )
I am sure that you would need to run the plugin from the Dashboard of the site in question, not whatever “super admin” place might exist.
I suggest just downloading the plugin and trying it out on your test server.
Forum: Plugins
In reply to: [Media Sync] Does it work for multisites?Hi!
I m not positive (I am not the plugin developer), but Media Sync uses standard WP functions, so I don’t see any issues with multisite.
Just to be sure: Each site has it’s own media library and wp-admin dashboard, right?
The DB tables for each site are separate.Have you tried setting the scan directory?
wp-admin/options-general.php?page=media-sync-optionsMedia Sync Settings
Scan directory /wp-content/uploads/ …..I would think putting sites/25/ into the text box will do what you want.
Hi!
Are you using the Woo-supplied Stripe plugin or a 3rd party one?
As I remember it, the Woo-supplied payment gateways require WC_Admin (at least parts of it) in order to run.Forum: Plugins
In reply to: [Extra Fees for WooCommerce] undefined variable v3.7.2No more visible errors.
Forum: Plugins
In reply to: [Media Sync] Import fails with 503 Service UnavailableSo, it turns out this issue is pretty much the “standard” one – and I don’t mean that negatively to either of you.
Pushing the “driver” to client-side solves the PhP limit issue that batch processes of all kinds tend to run into — but opens the door to throttles imposed by IMO unreasonable hosting. Such explains why this isn’t happening to everyone.
P.S. I haven’t had a chance to test the almost certainly unrelated issue I have/had. I note that it is on my horribly mucked up test server. If it happens on my staging or prod servers, I’ll open a new ticket.