Fee
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Photo Album Plus] Feature Request: support custom WP_CONTENT_DIRI guess this one is from before the patch:
Recursive log detected: Err Could not create /[…]/wp-content/uploads/wppa
After deleting it, de- and reactivating the plugin, there are no error messages.
Forum: Plugins
In reply to: [WP Photo Album Plus] Feature Request: support custom WP_CONTENT_DIRok… I had to de- and reactivate the plugin again after changing this option, for the folders creation. Sure that the depot folder should be on the same level as uploads and not inside of it?
Forum: Plugins
In reply to: [WP Photo Album Plus] Feature Request: support custom WP_CONTENT_DIRsingle site, yes all below ABSPATH
Forum: Plugins
In reply to: [WP Photo Album Plus] Feature Request: support custom WP_CONTENT_DIRGreat! Yes I can test the pre-release and give you feedback.
I deactivated your plugin via database, looked into your code and started some trials. There seem to be problems with the filesystem functions. I changed all lines in your plugin using get_contents and put_contents to use plain @file_get_contents and @file_put_contents instead. With this it worked and I successfully imported the desired template. But maybe you want to check this for other users in future.
Hey Vrunda Kansara,
thanks for your reply.
The error happens in my local development environment (as I wrote in first post). I always check the updates there first. As I wrote, I had to roll back to version 1.14.3, so my live installation still runs with this version. So there’s no install where you could take a look at (because it’s on my local drive). Are there any other advantages for you by using the ticket form instead of here?
So how can we step in there further?Regards, Fee
Hi there, could you take a look into this issue? I tried updating to all updates, e.g. to 1.15.2 today, but I always have to roll back (to 1.14.3) because the issue is still there. With 1.15.2 it crashes not only the admin scree, but the complete website with error:
Fatal error: Uncaught Error: Call to a member function get_contents() on null in /[…]/plugins/ultimate-addons-for-gutenberg/classes/class-uagb-admin-helper.php on line 282
- This reply was modified 5 years, 6 months ago by Fee.
Hi there, this will fix it:
change line #82 in wpbe.php from
add_filter( 'contextual_help', array( $this, 'contextual_help' ), 10, 3 );
to
add_action( 'add_help_tab', array( $this, 'contextual_help' ), 10, 3 );I reported this on github:
https://github.com/nlemoine/wp-better-emails/issues/24Hi @wpexpertsio, you’re right. It’s the latest version but I now performed another debugging against the other plugins. It’s been a plugin conflict, I solved it.
it’s everywhere in wp-admin screen (not in frontend), still in WP 5.4, too.
I now checked something on a complete new site: with the atomic blocks plugin installed and activated the warnings disappear. Disabling the plugin again throws the warnings with a dying page. Reloading the page then works again (with atomic blocks plugin enabled).
On the other site, where I tested before, we do not use the plugin at all.
So maybe there is a reference to the plugin inside the theme, that cannot be found if the plugin is disabled.Hi @atomicblocks theme authors, @wpengine @arrayhq @mindctrl,
did you take a look then?
Do you still maintain this theme? I’m wondering about this issue not being solved, other issues in the support forum not answered since months and no theme update since october?
I know it’s hard to maintain a free theme and I really appreciate your work, this theme has been one of the best out there, but please give us an update about your plans.My workaround for now in class-uagb-helper.php from line 1363:
$wp_filesystem = UAGB_Helper::get_instance()->get_filesystem(); if(!empty($uag_instance)): foreach ( $combined as $key => $c_block ) { $style .= $wp_filesystem->get_contents( plugin_dir_path( UAGB_FILE ) . 'assets/css/blocks/' . $c_block . '.css' ); } $wp_filesystem->put_contents( $combined_path, $style, FS_CHMOD_FILE ); endif;Forum: Fixing WordPress
In reply to: Request: set wordpress_test_cookie only on login screenHi Joy, thanks for your answer, but I think there’s a kind of misunderstanding. I’ll try to be more precise:
I do not want to set any cookie.
I do not want to change the behaviour of authentication cookies.
I want to be able to let visitors surf on my sites without any cookies for privacy reasons.I’ve now continued some debugging on different sites and found the issue.
The ‘wordpress_test_cookie’ is not set in pluggable.php.
In wp-includes/default-constants.php this cookie is defined as TEST_COOKIE constant. Via this constant the cookie is set in wp-login.php.
WordPress itself sets this cookie only when visiting the login page – exactly what I want. Of course, the cookie is set on other pages, too, if a login form is included in frontend.
Additionally this cookie is set by a security plugin I use, but it seems to be gone with an update of this plugin now.Forum: Plugins
In reply to: [Polylang] PHP Warning@chouby I’m a developer and really don’t like this statement “just set WP_DEBUG to false in production and that’s ok” because that’s no clean way of coding.
In my opinion it’s time skipping support for PHP < 5.6 as most providers already skipped that.
Your milestone 2.7 is 100% complete – when will this version be released? What’s missing?You’re great! It works. Thanks 🙂
