greuve
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: update-core.php throws 404I had a similar problem today (page not found on update-core.php) trying to auto-install 4.2.1 using Firefox. Switching to Chromium (I use Ubuntu) solved it for me. Note that before the switch I also deactivated all WP plugins. Also note that my Firefox is loaded with many add-ons, while my Chromium is completely bare.
HTH,
GerForum: Plugins
In reply to: [Plugin: Facebook] Failed posting to x Timeline. Error: nullThe flurry of replies in the few months that passed say it all. It was my old age after all . . .
Forum: Themes and Templates
In reply to: [Manchester] Possible bug?“picking up the towel” ….
In another post “Placester Inc.” wrote:
[…] add the lines of code below in your functions.php […]
add_filter('https_local_ssl_verify', '__return_false'); add_filter('https_ssl_verify', '__return_false');
And that concludes the exercise: I now have a working Placester Real Estate site on localhost…
All I have to do now is figure out why I wanted one :o)
Forum: Plugins
In reply to: [Real Estate Website Builder] API KEY !!I came here from another topic, however with the same problem. I can confirm that the above addition to functions.php solves the API key problem when running a (sandbox) WP site from “localhost”.
Forum: Themes and Templates
In reply to: [Manchester] Possible bug?I had the exact same experience just now – also using a local XAMPP install. The problem is caused by a php version incompatibility. Current XAMPP uses php version 5.4.7 and this version has tightened up the use of not properly instantiating objects and has changed the way you code for passing a variable by reference.
The first error can be fixed by explicitly instantiating the object. Change line 76 in blueprint.php from
global $placester_blueprint;
to
global $placester_blueprint; $placester_blueprint = new stdClass();
There is one more occurrence of this problem. Before line 136 in blueprint\partials\get-listings-search-form.php add:
if ( !isset( $form_data ) ) $form_data = new stdClass();
The error on line 139 is caused by incorrect (as of php 5.3) use of “pass by reference”. It is the function definition that needs to specify that a call is to be made by reference and not the call to the function (see also Kernighan and Ritchie – 1978 ;o). There are a few other places where this needs to be fixed. Simply remove the ‘&’ from the call and (if not already present) add the ‘&’ to the function definition.
Remove &:
line 139, 142, 156, 170 in property-details.php – amenities_but and translate_amenities
line 18 in compatibility.php – get_valid_property_list_fields
line 20 in formatting.php – validate_numberAdd &:
line 268 in blueprint/functions/formatting.php – amenities_butNext problem: the “Install it Now” button on the admin page returns an object not found, however I was able to install the plugin manually.
And here comes the next problem: need to confirm email address and that gets stuck. So head over to the Placester website, create a new account and copy the API key to paste into my WP site. Unfortunately the plugin refuses to recognise it as a valid API key.
Two hours of debugging later and I’m now faced with a nag-screen every 5 seconds. Time to throw in the towel…
Forum: Plugins
In reply to: [Plugin: Facebook] Failed posting to x Timeline. Error: nullJzs hly Rtzingr … I don’t want to build a rocket … i just want MY website to copy output to MY fb page. The stuff I had to go through after the above is surreal, so i’ll refrain from an attempt to describe. Suffice to say that I would be surprised to see an approval “after 3 business days”.
Forum: Plugins
In reply to: [Plugin: Facebook] Failed posting to x Timeline. Error: nullffs … so i actually got to the next step … I had to create another wordpress accound (other than admin) with rights to only create posts. Then used that to create a new post and logged back into admin to publish the post and this time no error showed up.
Hurrah … but a rather insane workflow.
Anyway it now allows me to submit, but warns (?) me of the following:
Built-in Action Types require that you provide instructions for using your app’s Open Graph integration as your Open Graph Test User in a functioning test environment. Failure to provide a functioning test environment will result in rejection of your Action Type.
And a whole bunch of other stuff that I can’t copy/paste.