Mrbigp
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Custom fields on front end HELP (oldest subject ever?)No you answered my question. It seems it is a PHP thing. I sob.
There seems is no magical plugin that makes a custom page by making custom post type, allowing custom fields and then voila! It works.
Im sure this isn’t a hard thing to hire a PHP programmer to do.
Forum: Networking WordPress
In reply to: Superadmin login – which site?Oh goody, I see, a secret hidden super admin area!
Can’t wait!
Thanks
Forum: Hacks
In reply to: Hard coding category to custom post typeAhhh I see, I get it now. Thanks south for your help.
Forum: Networking WordPress
In reply to: Continuous master templateAhhh got it ok well it’s good to know one tweak can update the many, I guess that’s one main reason why multisite exists! Thanks
Forum: Networking WordPress
In reply to: Continuous master templateThanks for this – Ah ok…sooooo, if I have this right.
When a site is cloned for the first time from the one you decide is a template, then all of those sites share the same *theme*…I guess that makes sense.
Now along comes a new install – the granddaddy one that is going to aggregate categories into a shared blog, for example’ using something awesome like WPMUDEV’s Autoblog – https://premium.wpmudev.org/project/autoblog. Now this one is going to *look* the same as the clones but have different widgets and things. Essentially it uses the same *theme* – not literally sharing the theme, but I suppose it can have its own version of the theme.
So essentially:
1) Create all themes that want to be cloned and mass tweakable from a template blog
– edit template blog and all of its clones share the same theme, this one tweak to the template updates them all.2) To create the granddaddy blog – do a fresh install of a blog and then install the theme all by itself, afresh.
– edits to this blog’s themes are only applicable to itself, as one would expect.This I do suppose would mean that the theme files live in one place where they can be hacked up for the clones, and then also a different set the theme files lives in the granddaddy blog’s theme folder.
So for all intents and purposes the clone site share the same themes folder in the templates blog’s themes folder, and the granddaddy’s theme lives in its very own themes folder.
The granddaddy blog then sucks in certain things from the clones into what looks very much the same as the templates blogs, but with it’s own bespoke tweaks and settings.
If this is the case it makes sense and its almost so obvious I’m almost embarrassed to have asked.
If this isn’t the case I’m more confused now than I was before!
Forum: Hacks
In reply to: Hard coding category to custom post typeAhhh ok, so a custom post type essentially makes itself a separate classification in the database, essentially making all of those custom posts have the same attribute – that of ‘recipe’.
I guess I was thinking it might be a way to make sure that the recipes could be listed in existing WordPress functionality, but I suppose having a link in the menu to the custom posts (“recipes”), or even linking them together in a list elsewhere does the same thing, am I right in that’s what you are saying?
I can also see how custom taxonomy could work, essentially on the right of the edit page in the CMS would be a new heading for the custom taxonomy called “Recipe Type” or similar, then underneath the heading would be all the categories that are only applicable to the post type category. Is that right?
I think it’s all becoming clearer now!
Forum: Hacks
In reply to: Hard coding category to custom post typeThanks, that could work somehow, but ideally they still want to categorise something as maybe, breakfast, lunch or dinner as a minimum.
Maybe in the code there is a hidden field that doesn’t show up in the CMS, called ‘recipe’, maybe it just shows up as a category on the front end. Even hacked if I know what and where to paste a snippet of code…