Open JulesWebb opened 10 years ago
Just delete that line (and line 58), all it's doing is setting the page title in the module control panel.
Hi Iain
Thanks for the prompt response! I did as you suggested and below is a screenshot of the Selectatron Migrator settings panel. I don't see the option to 'Convert to EE Relationship Field'
I'm thinking it should be in the last column on the right, or am I missing something?
Thanks so much for your time. Jules
Did the old field have the setting to store selections as native relationships selected?
Sent from my iPhone
On 8/05/2014, at 10:30 am, JulesWebb notifications@github.com wrote:
Hi Iain
Thanks for the prompt response! I did as you suggested and below is a screenshot of the Selectatron Migrator settings panel. I don't see the option to 'Convert to EE Relationship Field'
I'm thinking it should be in the last column on the right, or am I missing something?
Thanks so much for your time. Jules
— Reply to this email directly or view it on GitHub.
Honestly I don't know. When I look at the only field using this field type I get the error below.
channel fields > Group: Menu > Clicked on Field Label "Order"
Fatal error: Call to undefined method EE_Fieldtype::EE_Fieldtype() in .../expressionengine/third_party/the_selectatron/ft.the_selectatron.php on line 23
Yeah it probably isn't in need of a migration. Just delete the field, there's no need for the add-on anymore. Use a native EE multi relationship field, reselect the entries and update the template code.
Sent from my iPhone
On 8/05/2014, at 10:46 am, JulesWebb notifications@github.com wrote:
Honestly I don't know. When I look at the only field using this field type I get the error below.
channel fields > Group: Menu > Clicked on Field Label "Order"
Fatal error: Call to undefined method EE_Fieldtype::EE_Fieldtype() in .../expressionengine/third_party/the_selectatron/ft.the_selectatron.php on line 23
— Reply to this email directly or view it on GitHub.
Ok, I guess I was just trying to avoid reverting the site back to v2.1.3 another time in order to view the entries that use this field. I think there's only 3 so that's a plus ;)
Ha well yeah, for the sake of 3 entries it'll take about 5 minutes!
...well you can't blame a girl for trying to wk the automated route if possible ;)
Appreciate your time and input, I got everything sorted and I'm good to go.
Cheers! jules
Have the same issue here...
My orginal field did not have the option checked for "Store selected entries as native EE relationships?".
I use that field A LOT on like a hundred pages. Would it be better for me to roll back, check the box, then do a whole new update process ?
Checking the box won't go back and recreate all the relationships, only for new entries.
What's the issue you're having exactly?
Good morning.
I have update EE from 2.5.x to 2.9. Accessing pages with the Selectatron in CP gave me the line 57 issue. Fixed it using the method proposed above, but I the got the same error as JulesWebb :
Fatal error: Call to undefined method EE_Fieldtype::EE_Fieldtype() in D:\HTTP\XXXXX\Current\system_new\expressionengine\third_party\the_selectatron\ft.the_selectatron.php on line 23
My field did not have the setting to store selections as native relationships selected.
Thing is I have over a hundred pages that uses this field...
Thanks a lot !
Hi Iain
I'm doing a major update to a site I didn't create. The base EE version is v2.1.3 which is prior to EE's native relationship fields. But when I update to the latest version v2.8.1 I get the following error
Fatal error: Call to undefined method Cp::set_variable() in .../expressionengine/third_party/selectatron_migrator/mcp.selectatron_migrator.php on line 57
I'm assuming that EE has depreciated some of the templating language used. Is this something you can help out with?
Appreciate your time! Jules