Meta should application wide or project wide ? about metamagik HOT 13 CLOSED

Was easier than i anticipated.

from metamagik.

Yes, this would be nice, but would take a lot of code alteration I believe, not even 100% sure it's feasible without creating a table, because meta data table has basically three fields, id, name and value. I'd have to look into it.

from metamagik.

To explain, there isn't a field to hold a project_id

from metamagik.

Yes I noticed that there isn’t a project_is anywhere.

We could just alter the current tables - if no project I’d is specified, it’s application wide. If it’s specified it’s project wide

I will think about it, for now let’s keep it in mind

from metamagik.

I think for now, I'm good on this. It will be a lot of work to put this in, something I could perhaps revisit later down the road. I'll leave this open as a reminder.

from metamagik.

more notes

• the settings panel would never be accessible to anyone that isn't an admin, so a new config menu would have to be added into projects config.

• 'human_name' cannot be duplicated, or there would be issues, admin set fields would have to take priority.

• add project_id to metadata types table

from metamagik.

After installing the update, 0.0.8 the screen is empty / blank.
did I forget something?

from metamagik.

I understood. the metada extension is incompatible.
I deleted it and everything is ok ..

from metamagik.

Moved to separate issue #29

from metamagik.

Defiantly would like to see this. Currently while nice, I can't use it because I plan to have projects that wouldn't make sense to have fields from all the others.

from metamagik.

Its been requested a few times, and its on my long list of to dos.

from metamagik.

They never seems to end do they...

It's all good though, I'll keep an eye out for updates, cheers.

from metamagik.

Was easier than i anticipated.

Good to hear, thank you for adding that in!

from metamagik.