bristoltutor2

Funny you should mention this; my error logs are totally jammed up with rubbish like this related to Woocomerce.

I have exactly the same error message on 6 websites, using 3 different themes. What do they all have in common? WooCommerce Subscriptions (Ver: 2.2.13, the latest version, which comes with a warning that it hasn’t been tested on the current version of Woocommerce, Ver: 3.2.1).

It seems to be an automatic response to blame errors on users, whereas this kind of error is actually a frequent occurrence/problem with Woocommerce. Sell it first, fix it later, seems to be the ethos.

Thank you

Thanks for the answer, appreciated.

To be honest, one or two other issues cropped up today and I realised that although EDD is undoubtedly a super product, it isn’t really what I need. Without an ability to import data that is used in their addons (in addition to the core products) it means each product must be in whole or part manually created….which is fine of you only have a few. Our estimate is that it would take about a week to manually create/edit all the items we plan to add. Sob..

It looks like MemberPress will be the solution, to be honest.

Thanks for your time.

I’ll have a look at it now..
Thanks

Hmm, looking at the description it looks as if people have to enter details in a form to access a download. Only users who are already paid members and already logged on will even be able to see the page, so then asking them for their name and email address would not be a good idea.

Is it not possible to just go from someone selecting a download to actually downloading it, withut ANY form of extra step?

thanks

Hell, I was being polite. We just tried to export the data we had imported, wondering if it might be useful, and realised that when we try to export CPT ‘one’ we are able to export ACF fields from CPT ‘one’.

However, when we try to export CPT ‘two’ we are only able to export ACF fields from CPT ‘one’. Empty fields, in this case, obviously.

Now I know why my colleague “looked at” this program “a few months ago” but never put it to any use. It’s a bug-ridden nightmare. If you value your data or don’t have ‘Jack and Jill’ simple data, don’t risk messing it up by using this, free or paid-for.

We eventually gave up, I’m afraid. It took us almost two days to get almost nowhere so we cut our losses. To be honest, creating hundreds of little sub-import fields just to deal with the fact that allimport and the acf addon can’t cope with taxonomy fields that are set up in ACF is probably slower than importing data manually.

One additional note;
We discovered one dangerous facet to using Allimport when importing data to update existing records using the ACF custom fields addon…..

Select the CPT you want to update, select the relevant fields in the ACF section. At this point you need to know that you have to tell allimport to ignore any fields you are not entering data into, as it doesn’t ignore empty fields and will delete all existing data if you aren’t careful r miss the relevant box (on the next page)…

Next, go to step 4 and find the relevant box. You need to tell allimport to only import specific fields. Click on the box that says ‘import only these fields’. You might assume, as you’ve already had to specify which CPT you’re updating, that the fields shown (to include/exclude) would be those of your CPT. You’d be wrong.

If you chose to use fields like ‘tel_no’ with meaningful names in more than one CPT you’re going to need a couple of tabs of prozac because when you click the ‘import these fields’ tab you’ll see every custom field from every ACF CPT that you have no your site. With no indication as to which they belong. Don’t assume that the fields at the top relate to the CPT you’re working on. It might, but it might not. Depends on the name of your CPT, I think.

Get a coin and start tossing it. If you’re lucky, you won’t make a mess and will import your data into the right fields.

Ah, not to worry. I did the same with gravity and it works now, even if its a bit expensive.

Actually, cthomasfr, this seems to be a very common problem and it doesn’t have anything whatsoever to do with configuring by hand. I have a fresh install, wp uploaded to domain, unpacked and installed via the wp frontend installer. I can go into admin, no problem, but cannot access my site. It is an endless loop.

I originally had this happen with 4.4.2 and got so pissed off with looping through the ridiculous ‘config already exists’ (delete it so it doesn’t) and the ‘seems you need a wp-config’ (let wp create another) ‘seems you’ve already installed wp, clear your tables to reinstall’ loop that I deleted wp entirely, cleaned my entire db (luckily I hadn’t done a lot of work) and tried again.

It didn’t work.

I did the same, delete the whole damn lot, then installed 4.4.1 to see where that led me.

Absolutely nowhere. With an empty database and fresh install (on a domain that DOES NOT have another wp install) it is now doing exactly the same thing. Never seen this before and it has ruined my whole damn evening, wasted hours of my time.

It may be that the message ‘installing now’ only happens if you clear your database – but that means you have no website content or are happy to delete it all. Not a lot of help for other people with this issue on existing sites!

My install is in its own folder – yes, I’ve done it before and have around 20 wp sites installed the same way. I am not about to install it in root as that would require me to destroy with html site that already exists there and which I would be replacing.

Now, if anybody knows what the problem is or has fixed the same problem on their own install, I’d love to hear about it!