Jump to content

Archived

This topic is now archived and is closed to further replies.

vytfla

Documentation

Recommended Posts

vytfla

I just inherited a site that is currently using a child theme of Platform Pro. Is there any sort of documentation to help me navigate the folders? It's not structured by what I am used to and there are a lot of files that I can't find or hooks that I have no idea where I can edit.

Share this post


Link to post
Share on other sites
Danny

HI,

 

Unfortunately, Platform Pro has been considered a legacy theme for over two years and therefore, there is no live documentation. However, I will speak to our developers and see if there is still a copy somewhere, but I highly doubt it.

 

I would recommend upgrading to DMS, as Platform Pro is now legacy, feature frozen, will no longer receive updates and is now open source on GitHub.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
vytfla

Thanks. I'm working for a client that use platform pro so not sure they're looking for a new theme.

Share this post


Link to post
Share on other sites
Danny

As our developers are not online during weekends, would it be possible for you to list all your questions and I will see if I can answer any of them.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
vytfla

I don't really understand the files and folder structure; I'm used to the theme root folders having files like header.php, page.php, etc... with the php already there where I can go add or replace lines of code. I think that all the template files are within the 'sections' folder, but they're laden with so many functions and hooks I'm not familiar with how to edit it now do I see any of the typical code I'm used to seeing.

Share this post


Link to post
Share on other sites
Danny

Platform Pro has drag and drop functionality and therefore, that is why the structure isn't the same as a standard theme. Most of the hooks are self explanatory, for example:

 

pagelines_before_html - Means if you use this, what you use will be positioned before the html

pagelines_before_site - Means if you use this, what you use in the hook will be positioned before the site div

 

The sections folder contains all the sections, sections are drag and drop pieces of code that you or your user can drag and drop onto templates in the back-end. Most of the code in the sections folder is to make the sections works, so you shouldn't really need to mess around with that.

 

If you want to include code into the Header or Footer.php files, you can edit them directly. However, the best course of action is to use a child theme and hook into the header.php files using the hooks, rather than edit the files.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
vytfla

Hmm okay. I'm looking at the header now, and one thing I am trying to accomplish is using a conditional statement to change the primary nav on a certain page; I'm not sure how to hook that in because I have no idea what pageline hooks are hooks for the nav.

Share this post


Link to post
Share on other sites
Danny

If you go to WordPress Admin Dashboard > Platform Pro > Template Setup and then on any section, click the Advanced Setup, the section will expand and all available hooks for that section will be displayed.

 

https://cloudup.com/cxTBPYHiNx1

 

An alternative would be to try and see if the Menu Swapper plugin works with Platform Pro - https://wordpress.org/plugins/menu-swapper/ or try the IfMenu plugin, which adds conditional logic to menus - https://wordpress.org/plugins/if-menu/


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
scoop

LMK if I should have started a new topic for this...

 

Had just finished and purchased PlatformPro when you went to Framework which I did buy for another client - so site in question is only 3 years old - client wants a face lift not willing to pay for a completely new site - and I would like to give it to them under my maintenance contract fee. Their main request is color and a homepage change - most of which seems easy to accomplish in PlatformPro.

Problem is that they want what should be able to be accomplished with boxes (some all text some all images) to link to pages/sections on click.

The piece I can't get to work is that they want:

4 boxes in a row 
Feature slider
4 boxes in a row

Trying to create this in the content area only allows me one set of boxes  either above or below the feature slider - soapboxes don't seem to be an option as they are not responding to being 4 in a row even when added to the main config area - but are stubbornly staying as 2 in a row.

 

REALLY appreciate your help!!!

Frustrating - Thank you!!

Share this post


Link to post
Share on other sites
Danny

As far as I can remember, you won't be able to achieve this in Platform Pro. However, you can in PageLines Framework.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites

  • Similar Content

    • jeomiland
      By jeomiland+
      Hi guys
      Is there a place where people can find "Users Manuals" for some of the core stuff in Pl5? Like shortcodes and how to use and setup some of the Extensions?
      The Signup Extension is driving me nuts - can't see where to actually add it to a page, widget, section after installing/activating. Have run into this frustration with other things.
      Searched and found this on Github: https://github.com/pagelines/Docs
      These Docs Are No Longer Updated
      These docs were originally created for DMS 1. We are now at DMS 2 and these docs are no longer active. To get the most up-to-date documentation, please click the links below.
    • Audun MB
      By Audun MB+
      Just for reference if someone else needs to do this. 
      The Sitemap footer doesn't support nested menus, which makes it kind of pointless. Who doesn't have a nested site structure? Anyway, this allows for more finegrained control over the footer, while keeping the nice look. 
      Anyway, I liked the style of the sitemap, so I recreated it with sections. Here's the setup.

      Add one main container. Too allow for styling, give this the additional class "footer". Add a text section with the two social buttons shortcodes ( [pl_facebook_like] [pl_twitter_follow] ), place it to the left (and left align the text). Add another for the copyright/privacy text (right align the text). 6 columns for each text section, and font size should be around 80%.
      Add another container, place it above the two text sections. Give it the class "footer-border", and add a transparent bottom border to that class (see CSS below).
      Add a widget section with the three menus (you probably need a custom sidebar, I'm using the Custom Sidebar plugin). Next to it add a container again. In this container add a text section for your adress (left-align text), and a Social links section. Give the social links section the class "footer-social", left-align the text, set padding to 0.0 and set font size to 150%. Somehow the social links section escapes the opacity I set for the rest of the footer and shows as much darker, so used the custom class to adjust that to make it look nice.  Below is my full CSS/LESS for footer-styling (I prefer menu items to be normal text color instead of link color, but wanted the mailto link in my linkcolor (@linkcolor is defined at the top of my Custom LESS/CSS, you need to define it as well or just ignore that part of the styling). 
      /*footer styling*/ .footer{ opacity: .95; a { color: inherit; } a:hover{ color: inherit; text-decoration: none; font-weight: bold; } a[href^="mailto"]{ color: @linkcolor; } .footer-social{ opacity: 0.5; } .footer-border { border-bottom: solid 1px rgba(0,0,0,0.2); } } This is what it looks like:
       
       
    • tdiaz
      By tdiaz+
      When are the docs pages going to refilled? 
      ..and will the content they have replaced be made available somewhere else?
      A bit too far into a DMS2 project to drop it for Platform 5,  but it certainly gives the impression it will be a lot more of a peppy, positive experience, so I'll shoot for that as the second rollout of the site, but until then- the inbuilt links to content (Docs, sections, answers..) in DMS 2 are either 404 or empty. Perhaps a revision that redirects those pages to the old content so it's available where it's needed and not on the current site / product offering where it would could cause confusion and such.
      I will say, I got into Pagelines because my interpretation of it was that it combines the easy (better) parts of NationBuilder, Webly, et al- and allows one to still have ultimate control, where with the aforementioned platforms, you are basically .. SOL. 
       
      -BUT- it took a while for exactly what was going on, what all the pieces were, and what exactly the product really was, to click with me. 
      I might add that, it was looking at the Platform 5 preview that it all started to make sense. Because Platform 5 is not a huge clusterfudge of a pile of stuff that is all essentially the same thing.
      I wanted a theme, (WHP), then I saw the options, "oh, well if I get this, then I have 'more'" as the lineup gave me the impression that I can get "the theme" -or- I can get the theme and the framework, along with the PSDs and similarly related assets. 
       
      Platform 5 doesn't do any of that at all, but rather say "Here I am, this is going to be great!, Let's go!"
       
    • Danny
      By Danny+
      Hello, everyone.

      As you're aware, I am in the process of writing the documentation for the Platform plugin as well as creating introduction videos for all sections.

      Although this is a rough draft of the video, it should give you some idea as to what to expect from them. Please check it out on the link below, please do not share the video, as it is a draft and contains some mistakes.

      Another idea for the section docs after they're finished was to add the following:

      A reference to the shortcode that generates the section, so you can quickly see the shortcode that generates that section. Like so:
      [pl_section section="boxes" id="Unique ID"] Another idea was to include some of the sections classes, as a reference:
      .pl-sn-boxes .box-title .boxes-pad .boxes-media .boxes-icon Let me know what you think of these ideas and the video please.

      https://www.youtube.com/watch?v=nDSxOGFQbE0
    • micstepl
      By micstepl+
      the logo sizing option is
      not expalined not logical
×