WordPress.org

Ready to get started?Download WordPress

Forums

Creating Separate Blog-Feeds to Point Posts to 2 Different Landing Pages (7 posts)

  1. saurabhfiction
    Member
    Posted 1 year ago #

    (I believe I'm on an alpha version of WP 3.6 actually, according to source code.)

      The Current Situation
    : Right now, I modified my Settings in the "Reading" subcategory to have all my posts go to one page (not the main page) on my site. This works great, and is very handy.

      The Goal
    : I want to be able to set up a second (or potentially third, you get the idea) page where I can designate a separate blog feed for different posts to populate, so that I essentially have two (or more) separate, easily seen landing pages along the top of my WordPress site.

    I have a firm understanding of tags and categories, and all that is well and good, but in terms of setting up a separate blog feed -- and, being able to point specific posts to that blog feed / page -- I'm not sure that WordPress is able to easily do that. The settings seem to allow for just one instance of this, but it would be awesome if I could find a way to have a second instance of this on my site, where I have two 'landing pages' on the navigation menu, unrelated to tags/categories.

    A workaround that may be more feasible (that I haven't tried) is setting up a tag/category to essentially be a Page that appears in the nav menu. Is this doable? If so, anyone have any advice?

    Thanks for the help. I'm not experienced in coding, so the assistance would be greatly appreciated.

    Best Regards,
    Saurabh

  2. bcworkz
    Member
    Posted 1 year ago #

    This is possible. It will involve some coding, but I do not think it's too complicated. There's actually a few approaches you could take. I think the easiest would be to add a custom field to the posts to indicate which landing page it should be associated with.

    You can then either modify a current template or create a new one or several. The template(s) would alter the main query so that only posts with a particular custom field value are retrieved and displayed. If all blogs have the same look, one template could work for all of them. Or you can use different templates to yield completely different layouts.

    Another possibility that requires no coding would be to use the Multi Site variant of WordPress. It is essentially any number of individual blogs handled by one installation.

  3. saurabhfiction
    Member
    Posted 1 year ago #

    Thanks, bcworkz, for the explanation. Definitely makes sense that this would more feasibly be controlled from a posting standpoint. The look and feel of each blog feed will be identical; the only difference I'm going for is in content (with the goal being improved user navigation).

    I apologize if these questions are larger in scope than I'm realizing, but:

    -How would I go about modifying a template in WordPress?
    -How would I go about adding a custom field to a post?

    Would this come in the form of a plugin I'd need to upload to my wordpress? Not sure if it would help, but I looked into plugins for 'custom templates' -- and I found a plugin for it -- but every how-to guide I've searched for how to upload a plugin seems to be referencing a Plugin Uploader that I simply don't have in my WordPress Dashboard.

    If you could provide some information on the above questions, it would be a huge help. I seem to be hitting a wall with the help articles that are posted online, and every tutorial appears to be showing something in the Dashboard that, perhaps, my version of WordPress doesn't have.

    Thanks again!

  4. saurabhfiction
    Member
    Posted 1 year ago #

    I'm beginning to think my version of WordPress might be the culprit. I'm evidently on a an early version of 3.6. I don't know if this is just a result of poorly planned implementation, but I have no Plugin option in my Dashboard, nor can I edit my Theme under 'Appearance' -- the "Editor" option that's mentioned in so many WordPress articles simply isn't there.

    Will I be unable to modify my theme or create a new page template without this? Does anyone know why this was removed from 3.6? Seems like a really huge flaw that's preventing me from doing some pretty basic stuff.

  5. bcworkz
    Member
    Posted 1 year ago #

    3.6 is still in testing, most developers don't use the features you're looking for. I'm sure they will be functional by the time it's released to the public. For a production installation, I recommend sticking with the latest public release, currently 3.5.1.

    You can edit files and upload new plugins via FTP. I prefer this for editing files, even with 3.5.1, as I can maintain incremental backups, so it's easy to revert to earlier versions if I accidentally blow up the site.

    As for custom fields, read this article: Custom Fields You add the fields using the referenced functions. Your code is inserted into a custom plugin or child theme. Creating these is fairly simple, documentation can be found in the Codex.

  6. saurabhfiction
    Member
    Posted 1 year ago #

    Thanks, again -- I think any way I slice it, there is a bit of a learning curve before I can call myself an advanced WordPress user. I think the masses tend to just do the basic stuff on WP, but for people looking to do a bit more, I need to read up on things like PHP and the like. It doesn't sound too complicated, and the articles are definitely a wealth of knowledge, so I should be good with those.

    The unexpected hang-up is the non-Prod ready version of WordPress I seem to have. I'm led to wonder if this was just given to me by default, or if it was just something that slipped through for some users. I definitely didn't 'install' any version of WordPress in particular (I'm doing all my work via the browser), so for a casual user like me who's learning the more advanced ropes by necessity, it seems a bit more cumbersome than I originally anticipated.

    My experience w/ FTPs is limited; not sure if Core FTP Lite can allow me to do what I need, but I'll likely download the recommended FileZilla or something comparable to do the work I need to do. The alternative is waiting for version 3.6 to be finished.

  7. bcworkz
    Member
    Posted 1 year ago #

    Yes there is a learning curve :) You seem like an intelligent sort, and with your willingness to learn, I'm sure you will do well. It's awesome to know you can do pretty much anything you want with a site by simply modifying the code. No need to settle for anything the way it is. It is strange though about the version, you usually have to really want it to get it. It's not easy to stumble upon.

    For moving a few files back and forth, any FTP app will suffice. For heavy duty moving, such as reverting to 3.5.1, a full fledged FTP client will be required.

    If you're in learning mode, you don't want to be experimenting with your production installation. Even with a test installation, while you're learning, you will need to move files to and from the server a LOT. While doing so any one time is super easy and no big deal, doing so dozens and dozens of times gets old. I strongly suggest you install a web server locally on your computer to play around with. I found XAMMP to be very easy to setup, and of course, installing WordPress on it is also very easy. The ability to directly access server files without the need to use FTP is a huge benefit. It may not sound like much until you've worked with a local installation. Once you do, you will never understand why everybody doesn't do this.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags