pcvip
Forum Replies Created
-
Well, what worked was the insertion of an image from completely off-site (double test, right?; both that and the ability to insert a post w/o the library). And as I led with, this isn’t really your problem since that basic functionality IS working!
the stretch thing is problematic, of course.
And … I understand your code and assuming you named your own CSS correctly (<wink>), it should work, right? EXCEPT: the featured image never shows up in the archive or the carousel, with or without your exclusion declaration added, so honestly it would seem to be not-quite-right
Does the source code tell you anything (I know … LOOOOOONG)?
Actually, it sounds like you understood perfectly!
But it didn’t work. In fact, oddly, it worked exactly opposite of how it should have/you described; the image showed up in the post, but not in the archive pages/on the special elements, etc.
Also: “the image showed up in the posts” is technically accurate, but was stretched unbelievable; the original I used for testing was 126×126 px and it filled … well, a BIG area
Thanks you for trying; any other suggestions?
Oh (BTW) your software seems to make 2 postmeta entries per insertion and otherwise not touch anything … accurate?
Forum: Plugins
In reply to: [Attention Grabber (Hello Bar Alternative)] Compatible with WP 3.8it “works” in 3.8.1 for me, but with that said … it had a problem with my caching software when I first installed it (which resolved after a few minutes and a couple of cache resets), and … the customer.io integration doesn’t work at all because there’s no place for the customer.io API
Seriously … there’s no way to capture emails? NONE?
Forum: Fixing WordPress
In reply to: POSTS only: Unlogged-in users load, then go WSODNever mind … found the problem. It seems that as of its latest update, the WOOPRA plug-in (http://wordpress.org/plugins/woopra/) has gone rogue
Hey Woopra people … if you see this … you cost me a WHOLE DAY tracking down a mess of yours, not to mention you completely borked my web site for what I now believe could have been as long as ten days. Thanks for that.
Forum: Fixing WordPress
In reply to: Categories and Tags in 3.8 Gone Missing?OK … it was me, but … WHY …?
Seems that categories and tags are accessible under POSTS in the dashboard. And I presume they always have been? But MAN did I think they’d been killed somewhere. Marking resolved …
Forum: Alpha/Beta/RC
In reply to: 3.8 Dashboard (not a bug)I haven’t tried it, but someone claims to have come up with a solution:
https://digwp.com/2013/12/bring-back-single-column-dashboard-in-wp-3-8/
By the way, though: anyone else notice that categories and tags are now MIA from “At a Glance”? Anyone know how to get to them?
You’ve got it ; apologies for not realizing that was under MY control
Thanks, Maria … Got it !
Forum: Plugins
In reply to: [Graceful Pull-Quotes] Your statement about Shortcode cruft … ?Appreciate the reply. And you’re right on all counts; my point IS mostly philosophical because the non-purpose-no-appearance nature of a SPAN surely is superior to [shortcode] in the way you describe.
And if you’ve visited answerguy.com you see we’ve been using your plugin so … well, as you said, it really was mostly a philosophical issue.
THAT SAID: while your plugin leaves behind so little, and literally exactly the same thing for each instance of its use (ZIP down to almost nothing!), other items, like the pollution of the wp_options table perpetrated by so many plugins and themes, is an example of a similar but way worse problem: “I left behind invisible stuff [and] it swelled the bejesus out of your database”.
Nice job NOT doing that. And again, thank you for the reply!
Jeremy, I’ll do better. Here are two:
http://answerguy.com/influency-and-integrated-marketing/startup-packages/
and
http://answerguy.com/videopost/influency-building-blocks/
Notice that the SECOND one is a custom post type of a category created in-house, while the first is of a category created by the PREMISE plug-in.
Also, just for giggles, lemme tell you this: as of right now (9PM EDT), JetPack is showing 183 page views today, while Google Analytics is showing 667.
I’m accustomed to there being SOME disparity, but that’s nuts. Previous to this stuff getting all wiggy both tools ran in the daily range of 400-450. Further, I’m seeing 4.33 views per visit out of GA, which represents a significant jump from the 2.55 we were at FOR BOTH TOOLS before we relaunched using this new system, whereas WP/JP is showing those 183 page views being generated by at least 122 visitors (referral traffic thus far today), so something less than 1.5 pageviews per visit.
My theory is this: counted or not, sometimes or all the time, under whatever the prevailing circumstances are, I suspect that JetPack is somehow (somehow) tied to the main RSS feed. As I understand things each CPT has its own feed. GA is counting everything, and sometimes (huh?) JP is … not.
Which, if true, renders JP pretty much useless.
So hooray for me, I have a redesigned web site with traffic up 50% in 10 days, across metrics. I have greater user engagement. I rock!
But … I sure wish JetPack was working, you know?
Indeed, that’s there. In fact, it’s there even w/o the functions.php dummy, so the framework is, it seems constructed properly (hooray!).
Of course, the bad news is the whole “then why isn’t it working to start with?” issue!
Is the code in the footer the only delimiter that *should* control this working correctly?
Jeremy, I appreciate that. So here’s the rub:
I’m using Headway, which more or less eliminates the standard theme files, functionally replacing them with entries in wp_options. Of course, the files need to exist, and I’ve got a child theme that’s mostly empty but as of about an hour ago includes what I hope is the correct code (first three lines of what follows) in the otherwise-inactive footer.php file. What do you think?:
FOOTER.PHP====================
<body>
<?php wp_footer(); ?>
</body><?php
/* Prevent direct access to this file */
if ( !defined(‘WP_CONTENT_DIR’) )
die(‘Please do not access this file directly.’);/* WordPress and a lot of plugins require the function in this file, so I guess we have to use it :-(. */
wp_footer();HeadwayDisplay::body_close();
HeadwayDisplay::html_close();