This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

Problems with New Layout Builder 2.0.0 update

  • Creator
    Topic
  • #19274
    Alan Cohen
    Participant

    Jason:

    I updated to the new layout builder, and now I am having problems with updating my pages and the formatting of my custom tour types is screwed up. I am getting ready to publish shortly, and the timing could not be worse. Can I just uninstall the new builder and install the old version or do I need to restore the site from the latest backup.

    Your help would be appreciated as always.

    Thanks,

Viewing 4 replies - 16 through 19 (of 19 total)
  • Author
    Replies
  • #19339
    Jason Bobich
    Keymaster

    v2.0.1 of the layout builder is up. Let me know if there are other issues relating to the Layout Builder or Shortcodes plugin.

    Make sure to clear your browser cache after updating the Layout Builder plugin.

    #19351

    Working fine now! 🙂

    As always, Great support! 🙂 Thanks

    #19356
    Alan Cohen
    Participant

    I would concur with the above participant that your support is great!!

    So, I updated both the layout builder and the short codes, and have made some progress. I am no longer having problems with the toggle between visual and text editors, and it was a good idea by you to revert back to the wordpress 4.0 scrolling feature.

    The problem that I am still having is with the columns short code, in both the default template (pages) and the custom layouts (posts).

    I am attaching images and links so you can see. The first example is of two images that I am trying to line up side-by-side in one_third columns (nested within the two-third column portion of a page) using the default page template in full width. No matter what I do, I cannot get the images to appear side by side now.

    Here is how it looked prior to my upgrades (and how I want it to look):
    http://postimg.org/image/k799yhz7x/

    And here is how it looks after my upgrades:
    http://s16.postimg.org/uyklxmd5h/Ortelius_Itinerary_Maps_Column_Alignment.jpg

    The link to the page on my website so you can see the code is here: http://sv2.hepcatsmarketing.com/wp-admin/post.php?post=10598&action=edit&message=1

    The second example is of one-fourth columns (nested within the two-third column portion of a custom post type) using the custom layout “itinerary”.

    I was able to line everything up properly, but there is a lot of extra space between rows. This is to display the hotels for each city visited during the itinerary.

    See here: http://s27.postimg.org/7k0olvulv/Accommodations_Example_Custom_Layout_Itinerary.jpg

    Here is an example of how it previously looked:
    http://s3.postimg.org/82u3nnmmr/Custom_Post_Type_Tours_Hotels_by_City.jpg

    And, here is the link to the page on my website:
    http://sv2.hepcatsmarketing.com/wp-admin/post.php?post=16427&action=edit&message=1

    Please let me know your thoughts.

    Thanks,

    #19373
    Jason Bobich
    Keymaster

    The way you’re doing all of this is just very convoluted, I think. These column shortcodes were never meant to be nested within each other. Also, the “raw” shortcode isn’t a true shortcode. You can’t use it within other shortcodes.

    You have to think of things from a little different perspective. — Once you open up a shortcode like [one_third] — Now everything in here, until you close it, is no longer being processed by the WordPress page any more. It’s all being passed to a function in the shortcodes plugin now building the output for this portion.

    I would say if you’re going to the extent of having a page fill with this much nested HTML code, I just wouldn’t even use the column shortcodes in there. Just doing the HTML for the columns in there would probably be easier.

    Also, you’ve got to be careful how you’re constructing this HTML. You’ve now got inline elements like paragraph tags and spans, wrapping elements that are in DIV’sm (block elements), which is invalid markup. You’re going to end up with varying results in different browsers, as this gets more complex.

    So, for example, take this chunk that’s from your first example, that’s already within another column shortcode.

    <p class="small">
    [raw]
    [one_third]
    ...
    [/one_third]
    [one_third last]
    ...
    [clear]
    [/raw]</p>

    It can be re-written like this:

    <div class="row">
    	<div class="col-xs-4">
    		...
    	</div>
    	<div class="col-xs-4">
    		...
    	</div>
    </div>

    … I’m not sure how else you’d do it.

Viewing 4 replies - 16 through 19 (of 19 total)
  • You must be logged in to reply to this topic.