Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • @rectofossal

    I think you need to understand the nature of this type of collaborative work.

    Go PRO is, many times, a way to say ‘thank you for your great work for us’.

    Last time I did it was when I have paid for a year of support services, but I never get the password for that service.

    Best regards


    Going back to my first post, what I mean is: the file isn’t OK.

    When I upgrade the plugin, I need to recreate it using the command
    msgfmt -o wpsc-support-tickets-pt_BR.po

    By the way, after months using this plugin, I can say this is an wonderful job.

    I think you are giving us no useful information to get real help.

    I suggest you to disable all other plugins and change the theme in order to see this plugin works well.

    Conflicts between plugins are a little common for beginners like me.



    For me, it was enough to change WPLANG in wp-config.php and put the files in the folder named /wp-content/themes/wp-knowledge-base/languages.

    It worked as expected for the theme itself, but to translate bbPress Forum messages, you have to follow bbPress specific instructions.

    I suggest you try again and pay attention on caching.

    by the way, I am using pt_BR.

    Hope this helps,


    OK. I forgot to dig into the source code.

    I think you are right.

    thanks again..


    Thanks Stephen,

    But I am looking for specific instructions for WP Knowledge Base theme because I have translated the file en_US into pt_BR.po at wp-content/themes/wp-knowledge-base/languages folder. I mean this theme file has lots of bbPress messages and I think there is a way to use these messages.


    Hi Mark,

    I am afraid this don’t work for my config.

    This is because when using https my domain name is, but when using http my domain name is different –

    I think you should use a var like $URL_HTTP as I have suggested.

    In my config
    $URL is
    $URL_HTTP is



    A public visitor can access the/wp-admin/admin-ajax.php with the right url for http.

    Because your question, I looked at admin_url() reference – and now I have a suggestion to you:

    public static function wp_head(){
                    $URL      = admin_url('admin-ajax.php?action=wordfence_logHuman&hid=' . wfUtils::encrypt(self::$hitID));
                    $URL_HTTP = admin_url('admin-ajax.php?action=wordfence_logHuman&hid=' . wfUtils::encrypt(self::$hitID),'http');
                    echo '<script type="text/javascript">var src="' . $URL . '"; if(window.location.protocol == "http:"){ src="' . $URL_HTTP . '"; } if(window.location.protocol == "https:"){ src = src.replace("http:", "https:"); } var wfHTImg = new Image();  wfHTImg.src=src;</script>';

    This code preserves the old behavior, but changes the resulting URL when the protocol is http.

    Hope this helps. Let me know.


    Hi Mark,

    If you don’t mind, I want to help with the solution too.
    Look, I am very happy you pay attention to my words.

    If I understood right you will take admin_url() and will strip out “https” from the beginning.

    I feel if you help me this way you may create problems in other wordfence installations.

    Look at my case
    admin url
    site url
    not valid

    Let me know if I understood wrongly.


    I see what you are saying, but I disagree. I have three reasons for that (average user, best pratices and performance). I will focus on the first one, but if you would like I can explain all.

    If someone implements https, he or she must be prepared do deal with certificate problems, pay attention on expiration dates and check browsers support. In fact, most browsers will alert the user when something is not as expected. To avoid problems like that, I prefer https on my side (wordpress panel) leaving http to the average user.
    In my case, wordfence is getting live traffic info using https while the whole site is using http. It is not a bug. It´s more like a feature request.

    Wordfence is a ‘must use’ plugin and I thank you for this wonderful work.


    Hi Paul,

    I moved my site from Windows to Linux last week. Schedules started to work, but I still having problems with wp-cron and SSL. They are not related BakcupWordpress. However, I just want to help.
    The message is
    SSL: certificate subject name '*' does not match target host name ''


    @benedikt Mo

    I made a routine to fix filepath to images as SpillnerDesign said.
    I have tested it with the version 1.8.2 of Nextgen ScrollGallery, but I believe it fix BMo Expo plugin in the same way.
    I hope you would like this routine.
    side note: this is not related to “divide by zero” error.

    // mlsp
    /* the problem
     * I have noticed that scrollgallery create links to images using the following code
     *	SCROLLGALLERY_SITEBASE_URL . "/" . $picture->path ."/" . $picture->file
     * This works in almost all unix environments, but, in windows, $picture->path has the absolute fullpath to the image file and the link become invalid.
     * Like that:
    /* the goal
     *In the example above, E:/Home/httpdocs/wordpress/wp-content/gallery/2013 is the $picture->path and needs to be adjusted.
     *My goal is to remove the absolute fullpath part from the result of $picture->path.
    /* the strategy
     *	I have noticed the part I want to remove is the absolute full path to site I know as ABSPATH.
     *	Then I made a routine named nggSGStartPath that remove the ABSPATH from $picture->path and inserted the code
     *		$picture->path = nggSGStartPath(SCROLLGALLERY_SITEBASE_HOMEPATH,$picture->path);
     *	at the right place.
     *	There is one caveat, I mean, ABSPATH is like E:\Home\httpdocs\wordpress/ (note the first and the last slash) and $picture->path is like E:/Home/httpdocs/wordpress/wp-content/gallery/2013.
     *	I have to deal with it.
     *	We believe this routine does not break unix hosted systems.
    //this routine removes the start of a full path as e:\folder1\folder2 becomes \folder2 after removing e:\folder1
    //but startPath needs to be at least 2 characters long (this is to not touch fullPath when "" or "\") and be smaller than fullPath (this is to avoid an error in substr)
    //yet, we deal with slashes in StartPath, but not in FullPath (we trust FullPath uses only /)
    function nggSGStartPath ($strStartPath = "", $strFullPath = "", $intMinLen = 2){
     		if (strlen($strStartPath)< $intMinLen)              return (string) $strFullPath;          // does nothing
    		if (strlen($strStartPath) >= strlen($strFullPath))  return (string) $strFullPath;          // does nothing
    		$strStartPath = str_replace("\\","/", $strStartPath );  // any slash (\) must be translated in (/) to be web friendly as in FullPath
    		if (strtolower($strStartPath)==strtolower(substr($strFullPath, 0, strlen($strStartPath)))) {
    				// if we found startPath in the begining of FullPath then we cut it off.
    				$strFullPath = substr($strFullPath,strlen($strStartPath));
    				return (string) $strFullPath;
    return (string) $strFullPath; // does nothing

    hi all,

    I am using windows operating system as host and I have noticed the same problem in both BMo Expo and Nextgen ScrollGallery plugins.
    I think the problem comes from metadata info about images. In my case, they come from NextGen Gallery.
    Yesterday, I wrote an routine to strip ABSPATH info from $picture->path and the Nextgen ScrollGallery plugin is working as expected. Even the “divide by zero” error was gone. I consider I am in beta version and tomorrow after more tests I will have a final version to send to Benedikt Mo as a suggestion.

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