flamber
Forum Replies Created
-
Just tested by setting it to truncate 5 and it did it perfectly without messing with the extension.
@karzin You’re awesome – it works! 😉
I haven’t tested if the truncate function works, since they don’t use it – let me know if you need me to test that.Hi @karzin
It works perfectly on all sites – thank you for quick fixes!
Hi Pablo,
Thank you for the quick fix!
I can activate the plugin now – just getting used to the new settings dialog.I’ve just tested with the following filename and it doesn’t seem to behave good:
test-RENAME-file-æøåÆØÅ-"-'--_\:_.jsIt seems like the problem comes from the
\(I’m not using Windows). WordPress just calls the fileunnamed-file.jswith Title:_But I’m seeing the same error on Ubuntu 16.04 – both are running PHP 7.1
Hi Pablo,
Thanks for looking into this. I’m using Ubuntu 14.04
There is another error, which has something to do with the autoloader:
PHP message: WP Namespace Autoloader could not load file: /var/www/wp-content/plugins/file-renaming-on-upload/classes/FROU/class-plugin-core.phpOn one of my sites, it generate this error:
Fatal error: Uncaught Error: Class 'FROU\Plugin_Core' not found in /var/www/wp-content/plugins/file-renaming-on-upload/file-renaming-on-upload.php:29 Stack trace: #0 /var/www/wp-admin/includes/plugin.php(1882): include() #1 /var/www/wp-admin/plugins.php(164): plugin_sandbox_scrape('file-renaming-o...') #2 {main} thrown in /var/www/wp-content/plugins/file-renaming-on-upload/file-renaming-on-upload.php on line 29Forum: Plugins
In reply to: [Mivhak Syntax Highlighter] [Fatal Error] Compatibility with PHP 7.1.0PHP Fatal error: Cannot use lexical variable $fields as a parameter name.
This is a problem in https://ww.wp.xz.cn/plugins/wd-twitter-feed/ as well.
I’ve modified line 24+25 in FormCallback.php to the following and now it doesn’t crash, but not 100% sure if this is correct – seems to work:
$fields2 = $this->fields; add_action( 'wp_ajax_'.$slug, function( $fields ) use ( $fields2 ) {PHP 7.1 has been out for three months and is regarded as the current stable version.
Version 7.1 also fixed some issues with 7.0, so a lot of people have already upgraded.
http://php.net/manual/en/migration71.incompatible.php#migration71.incompatible.lexical-names- This reply was modified 9 years, 2 months ago by flamber.
Okay, someone had added text(?) to the two posts priority field with 100%. With the new version, when clicking save it gets cleared away.
And the below priority was fixed by 4.3.103.
Thank you 🙂
Here you go:
register_post_type( ‘omraader’, array(
‘labels’ => array(
‘name’ => ‘OmrÃ¥der’,
‘singular_name’ => ‘OmrÃ¥de’,
),
‘public’ => true,
‘show_ui’ => true,
‘show_in_menu’ => true,
‘hierarchical’ => false,
‘capabilities’ => array(),
‘map_meta_cap’ => true,
‘has_archive’ => true,
‘rewrite’ => array( ‘slug’ => ‘omraader’ ),
) );register_post_type( ‘juleleg’, array(
‘labels’ => array(
‘name’ => ‘Juleleg’,
‘singular_name’ => ‘Juleleg’,
),
‘public’ => true,
‘show_ui’ => true,
‘show_in_menu’ => true,
‘hierarchical’ => false,
‘capabilities’ => array(),
‘map_meta_cap’ => true,
‘has_archive’ => true,
‘rewrite’ => array( ‘slug’ => ‘juleleg’ ),
) );If you need something else or from the database, then please let me know.
Yahhoooo! version 4.3.102 saves and shows priority setting correct – thank you!
But still seeing the priority fluctuation.
sus.dk/sitemap-posttype-juleleg.xml still shows -10%. This post type is set to 0.5 and auto adjust.
sus.dk/sitemap-posttype-omraader.xml shows 100% on some, but the post type is set to 0.5 with no adjust.
Could that just be some cache in the DB, since I just replaced all the files in the old plugin with the new.Hi again 🙂
I’ve tested in Firefox (nightly), Chrome (stable) and even IE8. Conversion happens in the backend.
I cannot say if it’s another plugin that might be doing this – need to setup a dupe site to test that.
But I’ve just checked “xmlsf_post_types” in wp_options and it saves the comma value, so you might wanna throw in a str_replace to ensure there’s only dots.
One of the post types looks like this:
‘page’ => array ( ‘name’ => ‘page’, ‘active’ => ‘1’, ‘priority’ => ‘0,7’, ‘tags’ => array ( ‘image’ => ”, ), ),I got a guess that it might be connected to setlocale, which is configured on my server to LC_ALL=da_DK.UTF-8, since I needed some Danish value and date fixing for another project.
Sitemap is at sus.dk