Atavisionary

Ok, I am still having this problem where the loading the feed works, but I can’t actually update the page and save it. And it also seems to randomly change if it is willing to update or not. I wanted to add a new feed to my feeds page, and this problem again popped up. This time it was not the new feed that was the problem. When I tried to simply reload the exact same feed list that worked, updated, and saved a month ago, it would not let me update the page now. I don’t know why. This seems very fickle. The list of those feeds is at the end of this comment. I will note, that the page itself, as I saved it a month ago is still working fine. I just can’t update it or change it if I want to add new feeds.

I tried to follow your advice and I made a test page where I could use the short code instead, and it didn’t matter if I tried to do it in the classic editor or the new one. It doesn’t implement the shortcode. I know shortcodes work, because I use widgets in pages plugin and that short code works exactly as expected. Here is the link to the test page where the feedzy shortcode isn’t working.

• This reply was modified 4 years, 11 months ago by Jan Dembowski.

Here is a non-blogspot example link which does the same thing.

In the edit page, everything loads fine. It is only when I try to publish/update that there is a problem

Here is a screenshot.

View post on imgur.com

Ok, the solution for this is to view the source page and ctrl+f search from “atom+xml” and copy the link next to it. This atom feed link actually works, whereas the “rss+xml” link below it does not. Don’t know why, but that solves my problem.

Alright, I figured it out. I had to go into my web host cpanel and edit comments.php.

for ( var i = 0; i < commentForms.length; i++ ) {
							commentForms[i].allowTransparency = <?php echo $transparent; ?>;
							commentForms[i].scrolling = 'yes';
						}
I changed scrolling here from "no" to "yes"

I also wanted the height of the box to get a bit longer so:

$height = $params[‘comment_registration’] || is_user_logged_in() ? ‘515’ : ‘630’; // Iframe can be shorter if we’re not allowing guest commenting

I changed 315 to 515 and 430 to 630.

I am happy with the result, mostly (the “post comment” can still get pushed off the screen, but the scroll bar lets you get to it at least). Hopefully this doesn’t cause any other problems.

One last thing, I have already tried adding the overflow: scroll; and while it does created scroll bars they never become usable.

Alright, I thought of a temporary solution which is kind of ugly and doesn’t really solve the problem, but it does make it substantially less likely for someone to encounter the issue.

If you add height= 1000px; (or whatever) to the div#respond part of the css document it loads that box a lot larger so a comment would have to be that much larger in order for the error to be seen. Not nice, but that should reduce the problem until a better fix can be found using scroll bars.

div#respond {
background: #fff;
margin: 15px 0 0;
margin: 0.9375rem 0 0;
padding: 15px;
padding: 0.9375rem;
position: relative;
height: 1000px;
}

Thank you altright, that was very helpful. Below is the changes I made to the code to get the changes I wanted. I changed either font sizes and added !important or I changed the color to the one indicated

`changes, color

/* Current Item Indicator */
.sf-menu > li.current_page_item > a,
.sf-menu > li.current-menu-item > a,
.sf-menu > li.current_page_ancestor > a,
.sf-menu > li.current-menu-ancestor > a,
.sf-menu > li.current-menu-parent > a {
color: #907C6D;
}

.sf-menu > li > a:hover,
.sf-menu > li > a:focus,
.sf-menu > li > a:active {
color: #966533;
}

.sf-arrows > li > .sf-with-ul:focus:after,
.sf-arrows > li:hover > .sf-with-ul:after,
.sf-arrows > .sfHover > .sf-with-ul:after {
color: #907C6D;
}

}
/* Current Item Indicator */
.sf-menu > li.current_page_item > a,
.sf-menu > li.current-menu-item > a,
.sf-menu > li.current_page_ancestor > a,
.sf-menu > li.current-menu-ancestor > a,
.sf-menu > li.current-menu-parent > a {
color: #907C6D;
}
.sf-menu > li li.current_page_item > a,
.sf-menu > li li.current-menu-item > a,
.sf-menu > li li.current_page_ancestor > a,
.sf-menu > li li.current-menu-ancestor > a,
.sf-menu > li li.current-menu-parent > a {
color: #907C6D;
}

changes font size

blockquote {
color: #555;
border-left: 6px solid #966533;
font-family: “Lato”, sans-serif;
font-size: 20px;
font-size: 1.25rem !important;
line-height: 1.3;
margin: 0 auto 26px;
margin: 0 auto 1.625rem;
padding: 15px;
padding: 0.9375rem;
position: relative;
}

blockquote p {
font-size: 20px;
font-size: 1.25rem !important;
margin: 0;
}

blockquote blockquote {
margin: 15px;
margin: 0.9375rem;
}

blockquote cite {
color: #cccccc;
display: block;
font-size: 20px !important;
font-size: 1.25rem !important;
font-style: normal;
margin: 15px 0 0;
margin: 0.9375rem 0 0;
text-transform: uppercase;
}

.site-title {
font-family: “Montserrat”, sans-serif;
font-size: 64px;
font-size: 3.6rem !important;
font-weight: 700;
line-height: 1.3;
margin: 0;
padding: 0;
word-wrap: break-word;
}