Fox_Black
Forum Replies Created
-
Hm, I set up a new database for the new test installation, which I used so unfortunately that will not help here.
@ultimatemembersupport: Any further suggestions? Could you recreate the problem?
Best regards,
What did you do, that it is working now? I set up a fresh 4.9.8 WordPress installation with only UM Plugin activated and it is not working?
Best regards,
Hello @mahlee,
I have the same behaviour. Seems to be correct in the new version. You can still let create them by Ultimate Member > Settings: Click Button: Setting up default pages. That should create them and it works fine after that.
Best regards,
Hello,
just saw your thread. Have you tried to click first the cog icon > edit profile and then clicking on the profile image and choose “change photo”. That was my mistake first, that I thought it would ask me to upload a new picture just by clicking first on the profile picture, but it just takes you again to the profile page/reloads profile page.
Best regards,
thank you for your reply. The UM settings are all the default settings:
Max filesize for profile picture: 999999999
Cover Foto max filesize: 999999999
Profile Foto Thumbnail sizes(px): 40, 80, 190
Cover Foto Thumbnail sizes(px): 300, 600
Quality: 60
Image upload max width: 1000
Cover Foto min width: 1000I tried to upload a profile picture with a size of 2188x1213px and also with 800x450px. Both failed. (Upload actually works, but cropping seems to fail.
I increased the memory limit by adding the line:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
into the wp-config.php file. And increasing the memory in php.ini:
memory_limit=256MBut same problem as before. I am testing it with xampp wordpress installation locally. In Ultimate Member Version 2.0.25 it all works fine.
Best regards,
Forum: Hacks
In reply to: WP-API not recognizing WordPress login cookie?Hello,
I came across this issue too and needed a whole day to figure it out.
I found the same solution but I have a question to it. It seems to me, that the JS nonce script is only included in the WP-REST-API Plugin itself and not in the WP Core. In the WP Core there is no skript with: wpApiSettings. So at the moment the only documented way to send authenticated requests to the WP API is to activate the plugin and to inlude the script to get the nonce and send with the request.
So WordPress anounced big that they now included the Rest API to the core but lacked to include the correct way to make authenticated requests to it?
So at the moment you can use the Rest API in the core only for displaying public informations and you still need the Plugin for updating etc purposes, right?
Best regards,
Forum: Fixing WordPress
In reply to: tinyMCE QueryI found that question, while working with TinyMCE. I think he wants to know where TinyMCE Plugins are located in a wordpress installation, so I write it here for you, if you havent found it yet, and others:
TinyMCE Plugins are located in:
wp-includes\js\tinymce\pluginsSo it is possible for you to place here additional TinyMCE Plugins to add functionality to the WordPress TinyMCE. I added for example the AutoResize function for me here.
To use them it is not enough to place only the plugin here, you will have to use it later in your custom JS code, when you use the Editor in a plugin or expand the default TinyMCE in your plugin.
Forum: Plugins
In reply to: [File Away] Encryption=on doesnt work together with flightboxOh, okey. Thank you very much. 🙂
Forum: Plugins
In reply to: [File Away] Encryption=on doesnt work together with flightboxI have one additional question:
Is it possible to encrypt the Links of the thumbnails, too? At the moment the picture links are itself encrypted, but the thumnails are loaded from the download directory directly?Best regards,
Forum: Plugins
In reply to: [File Away] Encryption=on doesnt work together with flightboxThats okey, thank you for your reply 🙂
Forum: Plugins
In reply to: [File Away] Dynamically added File Browser with JavaScript/jQueryI have to thank you again! I found that you integrated a custom page template for fileaway, which I altered a little bit and I can use it for that purposes. Now it works nearly out of the box when I load that page via ajax.
You are really great and your fast response of supporting that plugin is really great, too! I hope I can afford a few coins to donate you in the next time!
Forum: Plugins
In reply to: [File Away] Dynamically added File Browser with JavaScript/jQueryThank you. I will use the described solution. Best regards,
Forum: Plugins
In reply to: [File Away] Update directory tree after fileuploadThank you for your reply. Okey, its okey its only a small idea for improvement but the plugin is really, really great! Thank you very much!
Forum: Plugins
In reply to: [File Away] Private Folder for each UserThank you very much for your reply! Wow, you are very fast!
I am really very sorry. I was searching for a long time for a such a plugin but didnt found one that siuts my needs. I tried first and read only the settings in file away form, and concluded too fast. While you answered I was reading the tutorials and it seems it could fit in.
Thank you very much for a great plugin and your fast help! I will go on and try it. I will write again when I read all and tried it with the dynamic paths.
Best regards,
Hello,
I followed this thread, because it also affected my storefront-child. Now with 1.5.3 update it seems to work all fine again! Good job and thank you for a leightweight and great theme!
You wrote, that now all child theme styles are enqueued automatically. Before (with Storefront 1.5.0) I had at the top of my child themes function.php:
add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' ); function theme_enqueue_styles() { wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' ); wp_enqueue_style( 'child-style', get_stylesheet_directory_uri() . '/style.css', array( parent-style )); }that enqueued the styles manually, as it was the new recommended way from wordpress. I see, that I now doesnt need that to enqueue my child themes style, because this is done automatically. I removed it and it works.
My question, only to understand whats going on, is why doesnt worked my manually enqueueing with 1.5.2. In that thread there is a workaround posted by: @amor that looks like my code. I also tried that code form that thread and it did also not work for me? Perhaps somebody could clarify it?