Title: GregM's Replies | WordPress.org --- # GregM [ ](https://wordpress.org/support/users/gregm/) * [Profile](https://wordpress.org/support/users/gregm/) * [Topics Started](https://wordpress.org/support/users/gregm/topics/) * [Replies Created](https://wordpress.org/support/users/gregm/replies/) * [Reviews Written](https://wordpress.org/support/users/gregm/reviews/) * [Topics Replied To](https://wordpress.org/support/users/gregm/replied-to/) * [Engagements](https://wordpress.org/support/users/gregm/engagements/) * [Favorites](https://wordpress.org/support/users/gregm/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 22 total) 1 [2](https://wordpress.org/support/users/gregm/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/gregm/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Alex King’s Share-This](https://wordpress.org/support/topic/alex-kings-share-this/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [19 years ago](https://wordpress.org/support/topic/alex-kings-share-this/page/8/#post-479279) * wsperuzzi: If you check the Readme, you’ll find instructions for manually inserting the Share This link in your template, rather than having Share This do it for you automatically. If you do that, and only put the link code in your template where you woud like it to appear (e.g., single.php) and not where you don’t want it (e.g., page.php), you’ll be all set. * And to anyone interested in eliminating the 55K of javascript library overhead caused by Alex’s otherwise excellent plugin… * It’s actually pretty straightforward to do, because the plugin relies on just one substantive capability provided by the prototype.js library: Position.cumulativeOffset, which allows the plugin to position the expanded form in the correct place over the top of your page content. If you nuke that line in share-this.php, set the form.style.left and form.style.top each to 0, change the CSS for akst_form to position:relative from position:absolute, and remove the pesky lines that load the prototype.js library in the first place, you’re almost there. The final 2 steps are just to replace all instances of the $() function with document.getElementById() instead and make sure you’ve manually inserted the form contents right below your form link in your theme (rather than, say, putting the form contents in the footer). * What’s the outcome of all that? * First, the form now appears and disappears from within your page content when you open and close it, rather than appearing over the top of your page content. Second, your visitors don’t have to wait for a 55K library to load in addition to your page content just on the outside chance they might click on the Share This link. * You can see it in action in the blog section of my [mental health information](http://counsellingresource.com/features/) site. * I wonder whether Alex would consider adding a simple user-configurable boolean at the start of the code so that those who want the extra 55K overhead can choose to do so, while those who would rather avoid it can switch it off without manually editing the code? * All the best, Greg * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Alex King’s Share-This](https://wordpress.org/support/topic/alex-kings-share-this/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [19 years ago](https://wordpress.org/support/topic/alex-kings-share-this/page/8/#post-479277) * I’m guessing Alex is a busy guy just now, so I’ll reply to my own question in case anyone else is interested… * Yes, it works fine to replace that ?p=postID structure with the permalink — just strip off the trailing slash if your permalink setup uses one. For example: * ` $posturl = rtrim(get_permalink($post->ID),"/") * Then in the relevant link line I mentioned in the previous post, replace that call to the blog URL with: * ` * IMHO, this should be done by anybody who doesn’t want to risk bots crawling a whole bunch of duplicate content accessed via the ?p= parameter rather than via the permalink. Yes, Alex has included a ‘nofollow’, and if every bot paid attention to that, there would be no problem with using the original URL structure, but not all bots do. (Having had my share of bad bot problems, I’d rather not take the risk…) * All the best, Greg * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Alex King’s Share-This](https://wordpress.org/support/topic/alex-kings-share-this/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [19 years ago](https://wordpress.org/support/topic/alex-kings-share-this/page/8/#post-479276) * Hi Alex, * I’m puzzled by the URL construction at line 428 of share-this.php 1.4, which seems to rely on a non-prettified URL structure. If I kill the non-prettified URL structure by replacing ?p=postID structure with a get_permalink and ?akst_action =share-this appended, this exceedingly cool plugin still seems to work fine, at least under the limited circumstances where I’ve tried it. * Is it OK to do that, or am I inadvertently going to break something and not realize it til it’s too late? * Thank you Alex! * All the best, Greg * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [MarsEdit ‘Keywords’ vs. WordPress ‘Post Slug’](https://wordpress.org/support/topic/marsedit-keywords-vs-wordpress-post-slug/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 1 month ago](https://wordpress.org/support/topic/marsedit-keywords-vs-wordpress-post-slug/#post-146711) * Hi Randy, * You asked why I would need to change the slug… * One answer is: because it’s a built-in feature of WordPress, and it’s there for a reason! 🙂 * But seriously, the reason *I* like to change the slug relates to why I use nice permalinks in the first place, rather than numerical database queries in my URIs. Specifically, I like a permalink to mean something useful and possibly even memorable. * So, suppose I wrote a post called “Here Are My Top 10 Reasons for Preferring Brief Post Slugs Rather Than Default Slugs”. I would probably choose a post slug like “why-brief-slugs”, or maybe “brief-permalinks”. That, to me, would make the slug useful and possibly even memorable. * But the default, automatically generated, slug would come out as “here-are-my- top-10-reasons-for-preferring-brief-post-slugs-rather-than-default-slugs”. That just doesn’t seem to me like a particularly friendly, useful, or memorable ending for a URI. * Still more broadly speaking, where WordPress offers built-in features for specifying different aspects of posts (e.g., whether or not comments are switched on, what the post title should be, what the post slug should be, etc.), I think it’s a good idea to expose those features through the API — the API which exists specifically to expose WordPress functionality to other applications. * On the other hand, I’m not the one investing time writing the XML-RPC code, so this is more of a wish for something I would find useful, rather than an argument that “thou shalt do it this way”, if you see what I mean. As far as the folks who *are* investing their time to produce the code, well, I guess I’m just mostly grateful that they do what they do in the first place! 🙂 * All the best, Greg * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [MarsEdit ‘Keywords’ vs. WordPress ‘Post Slug’](https://wordpress.org/support/topic/marsedit-keywords-vs-wordpress-post-slug/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 1 month ago](https://wordpress.org/support/topic/marsedit-keywords-vs-wordpress-post-slug/#post-146709) * Hi folks, * I’d like to second the suggestion to open up the post slug to access via XML- RPC. * Many of us prefer client-side environments such as MarsEdit for writing posts, as distinct from web-based environments such as WP’s built-in editor, but without access to the post slug via XML-RPC, it’s still necessary to make a special trip to the web-based editor to alter the slug after every post. * (Yes, I realize I could just write posts in Dreamweaver or GoLive or BBedit, and in fact this is what I always did before trying MarsEdit, but the latter is *much* slicker than writing a post in an XHTML editor and then copying and pasting into the web-based editing environment…) * I don’t know how much work it would take to make this possible, though — any thoughts from Podz or others? * All the best, Greg * Forum: [Everything else WordPress](https://wordpress.org/support/forum/miscellaneous/) In reply to: [an idea to spoil spammers “work”](https://wordpress.org/support/topic/an-idea-to-spoil-spammers-work/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 3 months ago](https://wordpress.org/support/topic/an-idea-to-spoil-spammers-work/#post-148608) * I would urge caution with this, folks: most of the leading search engines do not look favourably on sites which include hidden links, invisible to end users. Whether or not you are doing it for a noble purpose, this is still a deliberate attempt to offer one thing to the search engine and another thing to the end user, and in the context of building search indexes, this is called spam. * Just my tuppence, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Can’t use Bold, Italics, etc. (quicktags) on Mac](https://wordpress.org/support/topic/cant-use-bold-italics-etc-quicktags-on-mac/) * [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/cant-use-bold-italics-etc-quicktags-on-mac/#post-117399) * Hi likoma, I’m still using 10.3.5 until some widely reported troubles with 10.3.6 get ironed out (see macfixit.com, for instance), and my experience is like yours— Safari does not display the Quicktag buttons. Firefox, however, displays them just fine, so if you’re keen to do your writing in the WP window, I’d suggest giving FF a try. Personally, for anything longer than the briefest of posts, I prefer to write in a fully-fledged editing environment and then copy & paste anyway — but it all depends on how you like to write. Good luck, Greg * Forum: [Your WordPress](https://wordpress.org/support/forum/your-wordpress/) In reply to: [New Multi-Column Layout Integrated into Site](https://wordpress.org/support/topic/new-multi-column-layout-integrated-into-site/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/new-multi-column-layout-integrated-into-site/#post-115700) * Hi mpower, Thanks for your thoughts! niggles def.= ‘little things that bug me’ 🙂 Are there any things that particularly stand out as clutter? When you say lots of white spaces, do you mean on short entries, where min-height is set to keep that right-hand column from overflowing the bottom border? (Or maybe just too much white space in general?) Thanks again, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [No custom fields for static pages?](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/#post-115427) * ColdForged — Unbelievable!!!! I would have sworn that I shut this off days ago, but when I checked again tonight at your suggestion, Presto! There it was, enabled. I switched it off, and your code works, my code works, static pages work, and all is well!!! Thank you so much for persevering with all my questions. I probably would never have thought to go back and check that setting, but now that I have everything works precisely as I’d hoped! All the best, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [No custom fields for static pages?](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/#post-115424) * Hi ColdForged, Hmmmm…….. The fact that the code you supplied doesn’t work either is interesting: much like the other examples I had tried, a space is getting inserted between the initial less than sign and the question mark, and it’s all down hill from there — no eval. I haven’t been using any additional post massaging, but the really weird thing is that the space is getting inserted even when the‘ WP Unformatted’ plugin is enabled and the relevant custom field is set to 1 ( in an ordinary page, rather than a static page). So WP is STILL getting to my post text and fiddling with the code, even with a plugin set to prevent that. I’m befuddled… Perhaps I’ll trying enabling Textile 2 to see if I can duplicate your success with your example code… Oh, one last question: would you be able to say any more about the ordering of add_filter calls? I can see these being declared in the plugins, but I don’t know what they do (and couldn’t find any mention of add_filter in the wiki). Could switching these numbers around a bit improve the chances of one thing not messing with another? Thanks very much, ColdForged. I’m away for the night for now (I’m in the UK) but shall try again tomorrow… Thanks again, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [No custom fields for static pages?](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/#post-115418) * The plot thickens…………….. After more testing, I’ve found that code is getting botched even with Alex King’s ‘Unformatted’ plugin enabled, so it’s not wp_texturize that’s responsible for completely nuking the code… Moreover, I’ve also found that there are at least 3 different versions of ‘Run PHP’, written by 3 different people — and the version I’m using (James Van Lommel) turns out to have trouble handling almost all examples of PHP I’ve tested it with *except* for permalinks embedded in anchor tags (which was the job I originally wanted Run PHP for)… So, more questions for ColdForged or anyone else out there using (some variety of) Run PHP with static pages under 1.3a5: *which* Run PHP are you using? What sort of PHP are you successfully getting eval-ed? Thanks again, and Happy Weekend, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [No custom fields for static pages?](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/#post-115406) * Hi ColdForged, Looking at it again, I see that wp_texturize (presumably) is utterly and completely botching my included PHP code anyway — turning the entire page into a complete mess. Of course, I could switch this ‘helpful’ feature off with any of a number of different plugins — however, that again requires being able to specify a custom field so the plugin will know to switch off the evil interference from wp_texturize. So, back to the original question: is it intentional that static pages can’t have user-specified custom fields? Many thanks, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [No custom fields for static pages?](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/no-custom-fields-for-static-pages/#post-115403) * Hi ColdForged, Well that’s pretty weird… I’m not even sure where to start to trouble-shoot why it isn’t happening on my example page — but the source returned by the server is still full of PHP tags, even though ‘eval’ has been checked on the static page creation page. I wonder was your static page created with an earlier version, or with 1.3a5? Thanks, Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [wp_list_cats Unable to Return Single Category RSS](https://wordpress.org/support/topic/wp_list_cats-unable-to-return-single-category-rss/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/wp_list_cats-unable-to-return-single-category-rss/#post-115328) * Hi Beel, (The next morning…) Your suggested workaround works exactly as expected— many thanks! Greg * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [wp_list_cats Unable to Return Single Category RSS](https://wordpress.org/support/topic/wp_list_cats-unable-to-return-single-category-rss/) * Thread Starter [GregM](https://wordpress.org/support/users/gregm/) * (@gregm) * [21 years, 5 months ago](https://wordpress.org/support/topic/wp_list_cats-unable-to-return-single-category-rss/#post-115270) * Hi Beel, That sounds like a good suggestion — just circumvent the whole wp_list_cats query altogether! I’ll have to leave it a little while to try it out, as it’s dinner time now for me (past, actually), but I’ll put this into my theme as soon as I can! Thanks very much, Greg Viewing 15 replies - 1 through 15 (of 22 total) 1 [2](https://wordpress.org/support/users/gregm/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/gregm/replies/page/2/?output_format=md)