Tagged: x
-
AuthorPosts
-
August 16, 2016 at 11:15 pm #1134657
Hi there,
Would you mind providing your FTP login credentials as well? I like to check your templates directly.
Thanks!
August 22, 2016 at 4:12 pm #1142131This reply has been marked as private.August 23, 2016 at 3:45 am #1142760Hi,
Thank you for providing your ftp login.
Though upon checking, it seems like your server is down.
Kindly check and let us know.
http://screencast.com/t/bM02Po79NLbp
Thanks
August 23, 2016 at 2:02 pm #1143592It’s fixed now!
Please try again when you can.
Thanks!
August 24, 2016 at 3:39 pm #1145366Hi there,
Is this pointing on the correct folder, because the changes I made doesn’t reflect on the site ( https://x.dev.tstest.ca/resources/media/ ).
Two reasons :
1. I’m editing the wrong files because it’s pointing to different folder
2. WordPress is not picking up your templates
3. Cache feature, but I already cleared them. Host internal cache?
I added this code to test it but it’s being displayed. The code is still there so you could check.
<?php echo 'test'; ?>
Tested it in multiple places and it doesn’t take effect.
I just need to make sure if I’m troubleshooting the correct one because you have multiple URLs. The https://pods.x.dev.tstest.ca and https://x.dev.tstest.ca
Thanks!
August 25, 2016 at 5:16 pm #1147287Hi thanks for looking at this!
Ok so the correct url to look at is for https://x.dev.tstest.ca/resources/media/ and the file should be x>wp-content>themes>x-child>archive-media_post.php
I’ve used the pods plugin to change the url for the archive page of media_post custom post type to be /resources/media/
I can see the <?php echo ‘test’; ?> in that file. And I can see ‘test’ on https://x.dev.tstest.ca/resources/media/
so looks like you are in right file on right site.
I’ve deactivated the server side cache and the caching plugin for now
Any more help you can give is much appreciated!
Please let me know if you need anymore information from me.
Thanks so much you guys rock!
Cheers,
JesseAugust 25, 2016 at 9:45 pm #1147636Hello Jesse,
Upon checking, there is a pagination on that category page. It is just displaying at the wrong place. Please try adding the following custom CSS:
.post-type-archive-media_post .x-pagination { clear: both; position: absolute; bottom: 0; text-align: center; width: 100%; z-index: 9; display: block; }
Hope this helps.
August 26, 2016 at 12:15 pm #1148502Thank you!
That works! One little thing I can’t figure out still is how do I add some space above the pagination?
so that the gap is a bit bigger between pagination and the lowest masonry grid item?I’ve tried a couple things but it just doesnt’ work or pushes the button off the page.
Your help much appreciated!
Cheers,
August 26, 2016 at 7:18 pm #1148933Hello There,
Thanks for the updates!
Please update your release notes archive template first. You replace these lines:
<?php $stack = x_get_stack(); $style = x_get_option( 'x_archive_style' ); ?>
By using this:
<?php $stack = x_get_stack(); $style = x_get_option( 'x_archive_style' ); $cols = x_get_option( 'x_archive_masonry_columns' ); $condition = 'masonry'; ?>
And to change the position of the pagination, you can update your css code to this:
.post-type-archive-releasenotes .x-pagination { bottom: -15px !important; }
Hope this helps.
September 21, 2016 at 1:41 pm #1185178Hi,
Thanks for the help here with this!
one small thing still.
When I add the -15px to the bottom it cuts off the buttons a bit.
I can’t find how to fix that.Can you please help with some css so that the buttons do not show as cut off.
https://x.dev.tstest.ca/resources/media/Thanks!
September 21, 2016 at 6:52 pm #1185554Hi there,
Actually, the pagination should always appear at the bottom. And there is no need for CSS for that. Before we continue, why does each masonry item has this,
<style> h3, .h3 { font-family: lato; font-size: 26px; font-style: bold; } blockquote { font-size: 24px !important; font-style: italic; } blockquote p { margin-bottom: .3em; } </style>
The
<style></style>
is considered HTML element, the same level as<div></siv>
. It shouldn’t be added along with maonsry elements.This breaks the masonry order and put the pagination behind them. Would you mind deleting this, and then move the CSS to the footer, or customizer’s custom CSS.
Thanks!
September 23, 2016 at 4:04 pm #1188359Hi,
Can you please let me know where exactly you are seeing that css referenced above?
I’m not finding it easily.
Thanks for the help!
September 23, 2016 at 8:02 pm #1188623Hi there,
It’s on every
<article>
block. Please check the attached screenshot.Thanks!
-
AuthorPosts