ht39300
Forum Replies Created
-
This has been solved. The issue was a rather obscure plugin. Thanks all!
Forum: Fixing WordPress
In reply to: Can no longer edit HTML of homepage header or page headerThis has been solved. The issue was a rather obscure plugin. Thanks all!
Forum: Fixing WordPress
In reply to: Can no longer edit HTML of homepage header or page headerHi. Theme is twentysixteen-child (so, some minor mods I made originally to one of the standard themes). Settings->Reading has “home page shows latest posts” ticked so there are no URLs shown. Thanks!
Updating to v13.0.3 restored normal functionality here, including dashboard.
To work around the original problem, I had previously moved the wp-statistics plugin directory to wp-statistics-[date]. This restored dashboard (with no statistics displaying on the site, of course).
In any case, everything looks OK now after the update. Thanks!
- This reply was modified 3 years, 12 months ago by ht39300.
Fatal error upon upgrade here. Pages displayed but dashboard blocked. Manually renamed wp-statistics to wp-statistics-12-29-20 and regained dashboard access (but of course wp-statistics is now missing in action).
Forum: Fixing WordPress
In reply to: All notification emails ceased ages ago — except for tests!Hi. The obvious possibilities like those have already been checked. I control not only the WP site but the SMTP systems for the entire network. Other mail from the same machine where WP resides is delivered properly to me. The WP email test plugin also delivers email properly to me. So something else less obvious is apparently going on. Thanks!
Forum: Fixing WordPress
In reply to: Twentysixteen double date display in commentsNot practical. I need the time display on the posts.
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLThanks. In fact, one of the things I tried earlier was declaring the global $post and then calling permalink with $post->ID. Unfortunately, that didn’t work either!
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLJan, my apologies for the dupe posting. What I’m trying to accomplish is having the same pair of items at the bottom of each post, irrespective of whether it’s being viewed single page or as a full item on the home page. One of these is a G+ Follow badge. It works fine in both contexts because it uses a static Google URL that is independent of the post URL. The other is the plusone button. It needs to act based on the URL of the current post. I have that working fine in the single page view instance. It’s the home page view instance where I have not been able to find a way to get the correct post URL to pass on to the G+ API as I do in the single page view instance. Thanks!
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLRemarkable that such a basic functionality is so clouded in unhelpful mystery and such a seemingly opaque architectural framework.
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLI’d skip Ad Inserter for this and just put the code in my child theme index.php (or wherever) if I knew how — but I really don’t know enough about the WP architecture at this point.
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLAll I have is the code shown above. It’s in an Ad Inserter plugin tab, set to display “After Content”.
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLThe code is being inserted via the Ad Inserter plugin — so I’m unsure of what you need to see from there. Thanks.
Forum: Fixing WordPress
In reply to: Social Share for post in index, always wrong URLThanks. That just results in the LT/RT codes showing up on the rendered page, and it still doesn’t work.
Here’s some more detail. On individual pages, this code works to display the G+ button and Follow badge:<g:plusone annotation=”inline” <?php echo the_permalink() ?> ></g:plusone>
<!– Place this tag where you want the badgev2 to render. –>
<div class=”g-follow” data-annotation=”bubble” data-height=”24″ data-href=”//plus.google.com/+[User]” data-rel=”author”></div>For the home page, this code does successfully display the follow badge at the end of each post on the home page:
<!– Place this tag where you want the badgev2 to render. –>
<div class=”g-follow” data-annotation=”bubble” data-height=”24″ data-href=”//plus.google.com/+[User]” data-rel=”author”></div>For the home page, if I provide an explicit URL as in:
<g:plusone annotation=”inline” href=”https://www.blog.com/page001.html” ></g:plusone>
Then the G+ button and count (for that one particular URL) is properly rendered at the end of every post
displaying on the home page.The problem is getting the call to return the individual page URL into that construct on the home page, rather than an explicit URL, so the G+ call is correct for each individual page being displayed on the home page.
Thanks again.
- This reply was modified 8 years, 2 months ago by ht39300.
I found it. Priority 10 works perfectly. Thanks much!