Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Steve Dowe

    (@stevedowe)

    Hi Animesh,

    I apologise for taking so long to reply.

    I’ve just sent a request via the contact form you linked to. Really appreciate the help.

    Many thanks,
    Steve

    Thread Starter Steve Dowe

    (@stevedowe)

    Hi Kuba,

    Unfortunately I don’t really wish to share the sign-up page as it would reveal the site I’m trying to keep private 🙂

    I just modified the registration form with some additional text to explain that email is the only notification mechanism. If a user doesn’t want to be notified by email, then they are basically disinterested, so free to leave/deregister their account at any time.

    This kind of simplicity seems lost in today’s OAUTH2.0 world. Maybe I’m just old school…

    Cheers,
    Steve

    • This reply was modified 6 years, 10 months ago by Steve Dowe. Reason: Added "Maybe"

    If it’s happening in Chrome too, I’d be inclined to suspect something on your web hosting more than on your desktop. I have seen various posts on the web regarding mod_security settings being a bit too restrictive on the server (mod_security is an Apache web server module that can limit certain types of access).

    That being said, in my case I think I have isolated it to being a problem with cookies. It seems that when cookies have reached a certain age, the problem appears. I don’t get the problem in Chrome.

    So, I think although the symptoms are the same, the causes may be different.

    Who do you host with?

    Hi Jon,

    I’m trying to get to the bottom of this issue myself. I’ve seen it occur quite frequently over the past couple of weeks – but only in Firefox, not Chrome.

    Do you have any add-ons installed which affect cookies, javascript or otherwise make any other performance tweaks?

    Steve

    I’d be the first one to admit my code is not perfect and, at best, a hack 🙂

    I totally understand where Sebastian is coming from. I want to contribute to open source a lot, but what I can make time for is very little.

    The whole problem here seems to stem from Google’s implementation (or lack of it) regarding a standard scheme for titles. In terms of sq10’s original problem, this solution works. This is all I intended to fix, because that’s how I format G+ posts too.

    But we could start looking at some basic rules which cover a few post styles.

    For example:

    • Where we have a single opening sentence and then a break, use that
    • In the case of a paragraph as the first text block, extract the first sentence
    • When there is a break and then a sentence/paragraph, just remove the initial breaks and grab the first line, as above
    • In all other cases, for example where we can’t define a reasonable title length (if grammar is poor in the source post), then just substring to a certain length and cut it off

    Just my $0.02…

    Hey there,

    Ok, so I had this problem too and figured I may as well try to fix it.

    I made the following changes in g-crossposting/g-crossposting.php:

    First, change this:

    // create content
    		$post_content = $activity->object->content;

    to this:

    // create content
    		$post_content = $activity->object->content;
    
    		// Modify content to remove title
    		if(($pos = strpos($post_content, '</b>')) !== false)
    		{
    			$content_pos = $pos +4;
    			$stripped_title = strip_tags(substr($post_content, 0, $content_pos-1));
    			$post_content = substr($post_content, $content_pos);
    		}

    Then change this:

    // set title for post
    		if ($activity->title) {
    			$post_title = $activity->title;
    		}

    To this:

    // set title for post
    		if(isset($stripped_title) && strlen($stripped_title)>0) {
    			$post_title = $stripped_title;
    		}
    		elseif ($activity->title) {
    			$post_title = $activity->title;
    		}

    Optionally, nearer the bottom, change this:

    $post_content .= '<div class="g-crossposting-backlink" ><a href="'.$activity->url.'" target="_blank">'.__('This was first posted on Google+', 'g-crossposting').'</a></div>';

    To this:

    $post_content .= '<div class="g-crossposting-backlink" style="width: 100%; clear: both;"><a href="'.$activity->url.'" target="_blank">'.__('This was first posted on Google+', 'g-crossposting').'</a></div>';

    .. which creates a clean break for social media icons appearing after my post’s images. You could make it cleaner by editing the CSS file, but I didn’t bother.

    If you want an example of this in action, here’s my G+ post:
    https://plus.google.com/108862967958261109459/posts/RemQ2n4q4P6

    And my auto cross-posted blog post:
    http://stevedowe.me/2014/05/bad-boy-bakewell.html

    Hope that helps someone!

    Cheers,
    Steve

Viewing 6 replies - 1 through 6 (of 6 total)