Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

It seems I can't create page write panels with MF 2 #5

Closed
EivindFS opened this Issue Aug 2, 2011 · 6 comments

Comments

Projects
None yet
4 participants

EivindFS commented Aug 2, 2011

Hey guys,

It seems that you have removed the feature from Magic Fields in which I can create write panels of the page type. I can't find a way to do it anywhere in MF2. It's all centered around custom post types.

That's a great setback in one area of the product and I would really hate to see it go. In many ways, it would thwart the CMS capabilities of the product.

Would love to hear your thoughts on this.

Eivind

Owner

hunk commented Aug 2, 2011

You can create a post type with the same elements that a page.

Exactly that you need from a format page?

EivindFS commented Aug 3, 2011

Hi Hunk,

That will unfortunately not work.

Wordpress handles pages quite differently to posts. One issue is that I would have to change the workflow from using template files to using switches in single.php. That will take Magic Fields powered websites away from the natural ecosystem of Wordpress development.

More importantly, pages have their own permalink structure. If I have a page "contact", it will be domain.com/contact. Given a permalink structure %year%/%category%/%postname%, your suggestion will create domain.com/2011/uncategorized/contact. This is IMHO unacceptable and will essentially mean I can't use MF2.

The ability to create write panels as pages was an important and great feature that cannot be taken out if I am to transition to MF2.

Cheers!
Eivind

Owner

hunk commented Aug 3, 2011

well "Page" of WP is a post type, MF v2 tries to use the whole potential of post type, There are very much WP's code that is conditioned to only work with its elements, in these cases we can not do much.

you can set this options in you post type. in Advanced Options, check true Rewrite, and in Rewrite slug "page", refresh you permalinks settings. the permalinks for all elements under this post type is domain.local/page/name-post

respect to the template. for post type you can create specific template single-{post type}.php, example the name of my post type is "magazine" the template for show this post is single-magazine.php

check this http://codex.wordpress.org/Post_Types#Template_Files and http://codex.wordpress.org/Template_Hierarchy#Single_Post_display

But if to it you you does not work or does not convince functioning MF's V2, good we cannot force you to using it, Some time ago (Magic Fields Team) we decide not to do horrible hacks for this version

mmalta commented Aug 8, 2011

Hi Hunk,

I'm actually on board with EivindFS. I really love your plugin and it has helped me out a lot over the past year or so. Especially now with your Post Type and Taxonomy functionality. The one thing you're taking away is a bit painful, though.

Creating a write-panel for a page was a strong benefit for users / clients and is also easy on the development side because we could just plug this into a page template.

Being able to make a "Non-Duplicable Write Panel" and plugging it into a template was so easy.

Is this gone for good?

I also see a problem with users upgrading from 1.x to 2.x because this is written so differently (will lose all writepanels).

Just an idea, maybe I'm missing something, though. I just liked not having to have a whole menu item for something like "Home Page" that has it's own fields.

EivindFS commented Aug 9, 2011

Hi Hunk,

As far as creating a plugin that works well with custom post types and custom taxonomies, I think you have done a bloody outstanding job so far. I love it.

But if you are going to create not only a plugin that works well with custom post types and custom taxonomies, but which can also be used to create a fully featured CMS system with Wordpress, then dropping pages support is IMHO the wrong approach.

I doubt there are many users in the world who are more actively using Magic Fields than I am. I think I have used it for 30-40 client websites (which is why I'm disappointed you chose to go free. I WANT you to charge for it).

For ALL of these client websites, I used Write Panels set to page. If I had to change that, I would have to create websites that were simply less good and harder to update.

I hope you will query your user mass before you make this decision final. I see here that mmalta agrees with me and I believe many do.

If you choose to make this decision final, then I need to speak with you about how to create a plugin for your plugin that recreates this functionality for MF2. It is absolutely essential for me.

Thanks,
Eivind

Owner

gnuget commented Aug 9, 2011

With Magic Fields v2 our target is extending the new features of wordpress and unfortunately the pages of wordpress have a few unique features who can't be share between post types, so we can't do mucho for you.

Implement the feature to you are asking us means write a lot code for this (re-implement write panels, hardcoding the plugin in many places etc) just for make the compatibility with templates in post types.

With MF2 we don't want make the same mistakes to we did in mf1, one of the big issues of mf1 is to in this moment is almost inmaintenable, each release is more hard to put new features, is more hard patch bugs at this point mf1 require a lot of time for work fine and with each release require more and more time and efford, we don't want this for mf2, we are doing all to we can for preserve mf2 as simple as be possible for any issue can be addressed very fast and without much efford.

I know to this feature is very important for you but for now wordpress keep this features for his page post type.

We are open to any kind of help, if you have a elegant way to implement this feature just let us know and i'm going to do all the possible for implement it.

Or maybe we can looking for a different approach for do this think without need to create a post type with the pages features.

@gnuget gnuget closed this Aug 9, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment