centicon

I figured it out – I tweaked the code as follows and it works!

add_filter( 'mc4wp_integration_woocommerce_data', function( $data, $order_id ) {
	$order = wc_get_order( $order_id );
	$data['MMERGE1'] = $order->get_billing_first_name();
    return $data;
}, 10, 2);

@chickwithbob Oh dear. I only have Tribe plugins on one site, put together by a different developer but there are issues from time to time. Yesterday had to troubleshoot manually adding an order. Customer couldn’t book on an Event through Event Tickets Plus, so the admin sent her a paypal invoice and wanted to add her manually. You add an order through WooCommerce and the creation of the order is supposed also to add the person as an attendee. But no attendee created. Fired up a staging copy of the site, activated default WordPress Theme, and it all works. It seems like some custom code added to functions.php in Divi Child Theme is interfering ??

Good Luck!!!

I am now running the current version 4.10.5.1 with no issues.

It was a while ago now but at the time I rolled back from 4.10.0.2 to the previous version and kept it there until the next update was released, and have had no issues since.

Was quite drastic though, to have this plugin take my site offline. Since then I have always backed up immediately before updating any of the Modern Tribe plugins – “once bitten, twice shy”

also having the same problem with v 4.10.0.2

Fatal error: Uncaught RuntimeException: Error while making ‘tickets-plus.commerce.woo’: ‘tickets-plus.commerce.woo’ is not a bound alias or an existing class

Have sent you the code for 1.6.2 which works OK for me. Maybe more testing is required before releasing code changes?

I reported this issue 5 days ago with 1.8.1 wiping out redirects – see previous thread. Better to roll back to an earlier stable version IMHO. Testing on one live site is maybe not enough. I installed 1.8.1 on three sites and in all cases all redirects were erased when I went to edit. Have rolled back to 1.6.2 and that version works fine.

• This reply was modified 6 years, 3 months ago by centicon.
• This reply was modified 6 years, 3 months ago by centicon.

On Bellacouche.com with 85 redirects, 1.8.1 not redirecting (85 redirects)

Rolled back to 1.6.2

OK on Gaiahouse.co.uk I have 860 lines of redirects. I pressed “Save Redirect” and it removes all hard returns and puts all the redirects into one line.

I have replaced 1.8.1 on that site with 1.6.2

I just located a site backup from 19 July and fished out version 1.7.5.

When I activate 1.7.5, redirects are broken on this version also with barnowltrust.org.uk. This was the version that fixed the Bye Bye Hacker glitch, but I think I just assumed that redirects would work with this version on this site.

So I am rolling back to 1.6.2 again.

I have disabled caching on the hosting now. This is the situation

1.6.2 list of redirects is saved, redirection working nicely (yay!)
1.7.7 list of redirects is saved but redirection not working
1.8.1 list of redirects is not saved and redirection not working

With 1.8.1, redirection does not work at all, and pressing the “Save Redirect” button wipes out all saved redirects. Which means the plugin version 1.8.1 fails to do what it used to do in 1.6.2.

On barnowltrust.org.uk I have 400 lines of redirects – these get entirely wiped out by any editing actions in 1.8.1. I then have to downgrade to 1.6.2 to re-insert them (and redirects work with 1.6.2). Then I deactivate 1.6.2 and activate 1.8.1. I check my redirect list is there (if i try and edit anything or add a new redirect, the whole list gets wiped out) but then the redirects don’t work any longer.

So I am rolling back to 1.6.2 again, which I have retained from a site backup made in May before the “Bye Bye Hacker” incident in July.

I am not sure at which version our redirects ceased working. We noticed it yesterday. I have the plugin working on four or five sites, so it looks like I will have to roll back to 1.6.2 on those sites also.

If 1.6.2 is working and 1.8.1 is not, it doesn’t sound like a plugin conflict.

Update: Situation for me was exacerbated by the caching with my hosting.

1.6.2 list of redirects is saved, redirection working nicely (yay!)
1.7.7 list of redirects is saved but redirection not working

currently have rolled back to 1.6.2

I have been in touch with @zuda and gave them access to one of the affected sites so that they could better understand what happened.

I hope they will explain it here.

They responded very well once they knew about it, bit it’s important for us to tell the developer. They don’t necessarily check these boards, and within a very short time of my alerting them on Twitter they had fixed it.

@user7381 – yes thanks I already did that.

Only caused me 2 hours of being stressed out trying to figure out if this was some kind of malicious attack on 35 sites I manage.

I alerted @zuda last night via Twitter – it shocked them I think but they acted fast and have fixed it. https://twitter.com/Zen_Moments/status/1019316656911405056

Fortunately it turned out to be just a cock up.

• This reply was modified 6 years, 8 months ago by centicon.
• This reply was modified 6 years, 8 months ago by centicon.
• This reply was modified 6 years, 8 months ago by centicon.

This happened on four sites of mine.

Rolling back to version 1.7.3 didn’t fix it.

I didn’t notice at first that this hacked code creates an index.html in the site’s root directory and also in wp-admin directory.

Rolling back to 1.7.3 and removing the two index.html files fixed it, and turned off automatic updates

These guys are “security experts” – someone is having a laugh with them…

Thanks for your reassurance Mihai – nice to know you are still on board – you helped me a lot in the past with Gaia House website. I have been with WP Ecommerce since 2011, but have been getting nervous, as development seems to have slowed down and Michael Visser told me he is concentrating more on Woo Commerce – I bought Product Importer Deluxe from him, and then it turned out he seemed to have abandoned development of it, and he refunded my money. WP Ecommerce has declined a lot in usage and popularity, while Woo Commerce goes from strength to strength, so I have been worried that one day WP Ecommerce just won’t work any more, through not being kept up to date.

Any comments you can make would be useful – the main thing to know is that the core plugin WP Ecommerce is compatible with PHP 5.6 and is still being developed

These are the issues when I ran the compatibility checker:
WP e-Commerce – Store Exporter – Compatible – Warnings: 2
Latest version – I uninstalled as I don’t need it
Warnings:
FILE: /nas/content/live/gaiahouse/wp-content/plugins/wp-e-commerce-exporter/exporter.php
————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————–
299 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.
————————————————————————————–

FILE: /nas/content/live/gaiahouse/wp-content/plugins/wp-e-commerce-exporter/templates/admin/tabs-settings.php
————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————–
75 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.

WP e-Commerce MailChimp Integration Version 2.6 – Compatible – Warnings: 1
FILE: /nas/content/live/gaiahouse/wp-content/plugins/wp-e-commerce-mailchimp-premium/mailchimp/MCAPI.class.php
————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————–
2462 | WARNING | INI directive ‘magic_quotes_runtime’ is deprecated since PHP 5.3 and removed since PHP 5.4

WP eCommerce – Version 3.12.0 Compatibility = Unknown.
The plugin/theme was skipped as it was too large to scan before the server killed the process.

Gold Cart for WP eCommerce Version 2.9.8 ?Compatible?Warnings:?1
This is not the most up to date version of Gold Cart, but it works for SagePay
FILE: /nas/content/live/gaiahouse/wp-content/plugins/gold-cart_plugin-2.9.8/merchants/linkpoint.php
————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————–
371 | WARNING | Function dl() is deprecated since PHP 5.3
————————————————————————————–

MagPie PRO Product Import/Export Version 3.0.9
this is an old plugin we still use, but we will have to stop using it

FILE: /nas/content/live/gaiahouse/wp-content/plugins/magpie-ce/magpie_functions.php
————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————–
918 | ERROR | Using a call-time pass-by-reference is deprecated since PHP 5.3 and prohibited since PHP 5.4
————————————————————————————–
FILE: /nas/content/live/gaiahouse/wp-content/plugins/magpie-ce/index.php
—————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————–
1 | WARNING | File has mixed line endings; this may cause incorrect results
—————————————————————————–
FILE: /nas/content/live/gaiahouse/wp-content/plugins/magpie-ce/magpie_ajax.php
————————————————————————————–
FOUND 2 ERRORS AFFECTING 2 LINES
————————————————————————————–
608 | ERROR | Using a call-time pass-by-reference is deprecated since PHP 5.3 and prohibited since PHP 5.4
800 | ERROR | Using a call-time pass-by-reference is deprecated since PHP 5.3 and prohibited since PHP 5.4
————————————————————————————–