Forum Replies Created

Viewing 15 replies - 1 through 15 (of 31 total)
  • Thread Starter Ujiki.oO

    (@ujikioo)

    thanks for the quick reply.

    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank George Appiah .
    Thank you for taking the time to actually create the data.
    I suspect an automatic update performed by the WordPress system.
    At /wp-admin/update-core.php ,
    Button: Click “Re-install version 6.0.1” and install again by overwriting.
    As a result, the abnormal phenomenon no longer occurs.

    I want yours to provide one file with <b>MD5</b> hash value embedded for all the distributed WordPress files.
    For example, if yours provide “<b>WordPress 6.0.1.MD5</b>” file, the user amd I will check the integrity of all the files provided.
    <b>MD5 file</b>: Please provide the <b>download URL</b> for “<b>WordPress 6.0.1.MD5.7z</b>” !

    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank threadi.
    I suspect an automatic update performed by the WordPress system.
    At /wp-admin/update-core.php ,
    Button: Click “Re-install version 6.0.1” and install again by overwriting.
    As a result, the abnormal phenomenon no longer occurs.

    I want yours to provide one file with <b>MD5</b> hash value embedded for all the distributed WordPress files.
    For example, if yours provide “<b>WordPress 6.0.1.MD5</b>” file, the user amd I will check the integrity of all the files provided.
    <b>MD5 file</b>: Please provide the <b>download URL</b> for “<b>WordPress 6.0.1.MD5.7z</b>” !

    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank threadi.
    I had done :

    1. Backup MYSQL data base.
    2. One by one Deactivate to a plugins
    3. Just after Deactivate and check Edit button and Edit text

    The problem could not be resolved.

    I have to install back to version 6.0.0 , I worry about MySQL data structure….

    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank threadi for your quick responce.
    I will check them !

    Thread Starter Ujiki.oO

    (@ujikioo)

    Mr. George Appiah
    and everyone.
    It turned out to be my mistake.
    Plugin: Pretty Links defined SLUG with the same name.
    I moved it to the trash and it became normal.

    Thread Starter Ujiki.oO

    (@ujikioo)

    Dear Mr. George Appiah
    > Kindly give your site address so I can take a look and let you know what I find.
    Normal : https://e.fs4y.com/page/2/ and please click “Launch multiple LIVE Linux from one partition in USB memory?” (My WordPress does Google machine translation by your Browser preferred language type code) Your Browser will get new correct URL : “wordpress.fs4y.com/chgkona-sh/”. This is correct.

    Trouble URL : https://motpresse.fs4y.com/page/2/
    If you click the title “Launch multiple LIVE Linux from one partition in USB memory?”,
    system requests funny URL : motpresse.fs4y.com/category/…..

    Thank Mr. George Appiah .

    Hello everyone.
    There are two points to check.
    1. PHP version used by your Apache server?
    2. Are there any mutations (download error or upload error) in all WordPress files and all files under the plugin?

    I have been using this WordPress plugin for many years. By simply switching the server IP address of the DNS server, the main WordPress can be restored at any time. It runs on two different Apache servers based on Japanese and six different Apache servers based on English, and the operating status of eight Apache servers is https://fs4y.com/newentry/?#AliveButlersAndaDeadMan. You can check it with a GIF animation that you can check the operating status by clicking the button. WordPress JavaScript, CSS, images, etc. redirect URLs to a high-speed Apache server dedicated to DNS round-robin static data using the .htaccess function. If even one bit is small, it is redirected to a gzip file.
    In conclusion, CSS & JavaScript Toolbox is working fine!
    However, the PHP version does not work in 8, so I am reverting to the latest version of 7!

    I would like to ask Mr. wipeoutmedia to include the MD5 hash values of all files before distribution!

    # cd ..../wp-content/plugins/css-javascript-toolbox
    # find -type f -exec md5sum "{}" \; | tee AllOfFiles.MD5

    Each WordPress server automatically backs up MySQL on the core server, receives the automatically generated compressed MySQL data with WinSCP, saves them on my NAS, and imports it into 2 WordPress on XAMPP on my PC. , I’m exporting MySQL from XAMPP and importing it into various publicly available fully mirrored WordPress MySQL. All backup bash scripts and WIN batch scripts for simultaneous processing of YUICOM PRESSOR and CLOSURE-COMPILER are available from my WordPress contents FREE.
    Excuse me, everyone.

    PS: I’ve been deploying two officially featured plugins for some time and deactivating them without warning.
    1. wp-jquery-update-test
    2. enable-jquery-migrate-helper

    Did you check the PHP version?
    My WordPress was fine up to PHP 7.3!
    It became abnormal when I made it to PHP8.0.

    Thread Starter Ujiki.oO

    (@ujikioo)

    I am sorry. Please forget !

    Thread Starter Ujiki.oO

    (@ujikioo)

    Mr.! Thank you for your reply. Thank you for using your brain!

    Now, delivering 1-bit useless data to a visitor’s browser leads to global warming. It’s a waste of electricity at relay points in any internet network. Electricity is wasted even on the server that runs WordPress, and the browser caches data that is useless for the browser, and using the cache containing the useless data wastes power and wastes battery power. I will. I’m a 64 year old man, but can a young developer understand that even a bit of useless delivery is a problem for global warming? If you don’t understand, read my long WordPress article. https://www.facebook.com/ujiki.oo/posts/3256482351051074

    Yahoo / YUI COMPRESSOR and Google / CLOSURE-COMPILER are used for primary compression of all WordPress JavaScript (JS) and Style (CSS). We publish bash script and inspect it all at once. If you only have .min, it will automatically create the source and automatically check the timestamp and MD5. Simply send JS or CSS by right-clicking on Windows 10 to process JS with YUI COMPRESSOR and CLOSURE-COMPILER at the same time, and compare the file set with gzip secondary compression to use the one with smaller capacity.
    CLOSURE-COMPILER has a rule to change the variable name specified by JS typeof, so I think that YUICOMPRESSOR, which always treats undefined variables as global variables, is orthodox. I mentioned in the past about the existence of JS that YUICOMPRESSOR returns an error to WordPress, but even the latest WordPress does not improve. For example, WordPress still adopts and distributes the old jQuery that returns an error with YUI COMPRESSOR.

    By the way, in JS and CSS distributed in major version upgrade of WordPress, there is generally a source file full of comments for developers, and it is primary compressed with YUI COMPRESSOR or CLOSURE-COMPILER, The time stamps should be deliberately the same, or normally the time stamps in the .min file should be in the future.

    If the JS source file and the .min file are distributed with WordPress major version upgrade, is it necessary to verify which one WordPress should read? I put a special .htaccess to deliver the gzip file that browsers prefer, but if you gzip a .min file that has even a bit of useless data, it will still contain useless data!

    The bash script automatically checks for time stamp integrity, but the above report shows a non-time stamp consistent source and .min primary compression fileset. I want to know which is correct. If both are correct, I want to know which file the WordPress system goes to read. Copyright comments are useless for browsers. As the owner of WordPress, I just want to create and deliver a gzip file that is a little bit bit secondary compressed.
    Thank you!

    Thread Starter Ujiki.oO

    (@ujikioo)

    Thread Starter Ujiki.oO

    (@ujikioo)

    Version:Featured Image from URL:2.9.5;
    Site:https://motpresse.votre.space;
    Theme:Lovecraft 1.31;
    PHP:7.3.13;
    WooCommerce:;
    WordPress:5.3.2;
    Pages:4;
    Posts:52;
    Products:;
    Images without Dimensions:;
    URLs with Metadata:55;
    URLs:55;
    php-curl:yes;
    Plugins:
    – Akismet Anti-Spam (akismet)
    – All In One SEO Pack (all-in-one-seo-pack)
    – Classic Editor (classic-editor)
    – CSS & JavaScript Toolbox (css-javascript-toolbox)
    – Featured Image from URL (featured-image-from-url)
    – Google XML Sitemaps (sitemap)
    – Merge + Minify + Refresh (merge-minify-refresh)
    – Movable Type and TypePad Importer (movabletype-importer)
    – Post Snippets (post-snippets)
    – Really Simple SSL (really-simple-ssl)
    – Under Construction (under-construction-page)
    – WordPress Ping Optimizer (wordpress-ping-optimizer)
    – WP Multibyte Patch (wp-multibyte-patch);
    Active Plugins:
    – akismet
    – all-in-one-seo-pack
    – classic-editor
    – css-javascript-toolbox
    – featured-image-from-url
    – google-sitemap-generator
    – merge-minify-refresh
    – movabletype-importer
    – really-simple-ssl
    – under-construction-page
    – wordpress-ping-optimizer
    – wp-multibyte-patch;
    fifu_auto_alt:toggleon;
    fifu_class:toggleoff;
    fifu_clean_dimensions_all:toggleoff;
    fifu_column_height:64;
    fifu_content:toggleoff;
    fifu_content_page:toggleoff;
    fifu_css:;
    fifu_data_clean:toggleoff;
    fifu_default_url:;
    fifu_dynamic_alt:toggleoff;
    fifu_enable_default_url:toggleoff;
    fifu_fake:toggleon;
    fifu_get_first:toggleoff;
    fifu_grid_category:toggleoff;
    fifu_hide_cpt:toggleoff;
    fifu_hide_page:toggleoff;
    fifu_hide_post:toggleoff;
    fifu_image_height_arch:;
    fifu_image_height_cart:;
    fifu_image_height_ctgr:;
    fifu_image_height_home:;
    fifu_image_height_page:;
    fifu_image_height_post:;
    fifu_image_height_prod:;
    fifu_image_height_shop:;
    fifu_image_width_arch:;
    fifu_image_width_cart:;
    fifu_image_width_ctgr:;
    fifu_image_width_home:;
    fifu_image_width_page:;
    fifu_image_width_post:;
    fifu_image_width_prod:;
    fifu_image_width_shop:;
    fifu_jquery:toggleoff;
    fifu_lazy:toggleon;
    fifu_media_library:toggleoff;
    fifu_original:toggleoff;
    fifu_ovw_first:toggleoff;
    fifu_pop_first:toggleoff;
    fifu_query_strings:toggleoff;
    fifu_save_dimensions:toggleoff;
    fifu_save_dimensions_all:toggleoff;
    fifu_save_dimensions_redirect:toggleoff;
    fifu_social:toggleoff;
    fifu_spinner_db:100;
    fifu_spinner_nth:1;
    fifu_wc_lbox:toggleon;
    fifu_wc_zoom:toggleon;
    REST Routes:
    https://motpresse.votre.space/wp-json/:PHP;
    https://motpresse.votre.space/wp-json/:JS

    Forum: Fixing WordPress
    In reply to: jQuery 3.4.1
    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank you for your exact response!
    Your indication is correct.
    Replacing with the latest JQauery caused problems with multiple plug-ins with different authors. I returned to the original JQauery.

    Unfortunately, although it is a past asset of Yahoo !, an error occurs in the genius Yui Compressor and the JavaScript diet fails. Since it is an error in the error handling routine function, there should be no problem with the source.

    If possible, please distribute jQuery.js after dieting with Yui Compressor. In MT, all JavaScript is distributed sectary Yui Compressor, and the original source is attached with another name.

    If gzip compressed file is distributed at the same time, it will be kind, but over 500 JavaScript (.js) and style (.css) are dieted and gzip compressed and used in my WordPress.

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    # for .js.gz & .css.gz
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond "%{REQUEST_FILENAME}" \.(js|css)$
    RewriteCond "%{REQUEST_FILENAME}.gz" -f
    RewriteRule .+ %{REQUEST_URI}.gz [L]
    # for .min.js.gz
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond "%{REQUEST_FILENAME}" ^(.*)/([^/]*)\.js$
    RewriteCond "%1/%2.min.js.gz" -f
    RewriteRule ([^/]*)\.js$ $1.min.js.gz [L]
    # for .min.css.gz
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond "%{REQUEST_FILENAME}" ^(.*)/([^/]*)\.css$
    RewriteCond "%1/%2.min.css.gz" -f
    RewriteRule ([^/]*)\.css$ $1.min.css.gz [L]
    # for .min.js
    RewriteCond "%{REQUEST_FILENAME}" ^(.*)/([^/]*)\.js$
    RewriteCond "%1/%2.min.js" -f
    RewriteRule ([^/]*)\.js$ $1.min.js [L]
    # for .min.css
    RewriteCond "%{REQUEST_FILENAME}" ^(.*)/([^/]*)\.css$
    RewriteCond "%1/%2.min.css" -f
    RewriteRule ([^/]*)\.css$ $1.min.css [L]
    </IfModule>
    AddType "text/javascript;charset=UTF-8" .gz
    AddType "text/css;charset=UTF-8" .gz
    AddEncoding gzip .gz
    Thread Starter Ujiki.oO

    (@ujikioo)

    Thank you for your advice !
    > what you want to do or if he could provide a solution for that.
    I had modified the unique PHP file “content.php” of the Theme Lovecraft myself.
    It was very nice to wrote my question at this page, becase I got the best hint !
    The result : I will be able to erase all data under the “/wp-content/uploads” This result will be able to speed up my WordPress main processing.
    I made the content about that how to hacking PHP file “content.php” : https://motpresse.votre.space/revisedfeaturedimagefromurl/#post-1708
    Thank you and accessed everybody.

    https://twitter.com/andersnoren?ref_src=twsrc%5Etfw

    • This reply was modified 5 years, 8 months ago by Ujiki.oO.
    • This reply was modified 5 years, 8 months ago by Ujiki.oO.
    • This reply was modified 5 years, 8 months ago by Ujiki.oO.
Viewing 15 replies - 1 through 15 (of 31 total)