Open DavidWells opened 8 years ago
The lead update stops sourcing event data recorded in the activity tav out of meta pairs and stores event data into a inbound_events table. This opens up our event logging (form submissions & cta clicks & email clicks & unsubscribe events & custom events) to better/faster/more complex queries.
The data migration is necessary because Leads 'Activity' tab is looking to the inbound_events table for the data now instead of calculating the data via meta pair storage.
An FYI though, lead page views and conversion paths are still stored as meta data.
Batch update is breaking geo data
Before batch update:
After:
The batch processing does not alter the geoobject nor the normal upgrade routines: https://github.com/inboundnow/leads/blob/master/classes/class.batch-processing.php#L90-L200 https://github.com/inboundnow/leads/blob/master/classes/class.activation.upgrade-routines.php
It has to be a deeper issue: https://github.com/inboundnow/leads/blob/master/classes/class.metaboxes.wp-lead.php#L700-L789 https://github.com/inboundnow/leads/search?utf8=%E2%9C%93&q=wpleads_ip_address
Not sure what at the moment.
Maybe an auto update on the geo data and the 3rd party service was down.
I have a ton of leads on my personal site.
What exactly is the "Leads plugin requires a database upgrade : Run Upgrade Processes" doing?
Dont wanna run and wait if I dont have to
Perhaps updating the message to users about why they need to update would be helpful