gavsiu

That worked for the placeholder. Thanks. I read that part of the docs but forgot about it.

The asterixes, however, were unaffected. Is there a way around this? I basically copied and renamed woocommerce_form_field and removed the asterixes for the required fields and put that in functions.php.

I can’t show you the test site because I’m developing it on my internal network and it has no internet access.

In trying to resolve this, I have commented out all my wp_enqueue_script, so the only JavaScript loaded should be WordPress and plugins. The code above was inserted into functions.php.

The main thing I wanted was to change the placeholder and remove all * on required fields (not removing the requirement) and just put “Optional” under the few fields in the description.

I have found that to remove the asterixes, I had to duplicate the function woocommerce_form_field and modify it.

If I use the original function, the problem with the 2nd address line placeholder persists (also would be the only thing changed).

This is what I see without JavaScript.

This is what I see with JavaScript.

Thanks

Can you add it back to the WooCommerce settings page? I’m ok with it appearing in the new location also, but it was easier to access it before.

@emj This does not work for the free version. Copying jquery.yith-wcwl.js and renaming it as wishlist.js breaks the page. Skipping that step and adding the snippet on that page to an existing scripts file sort of works, but adding an item to the wishlist creates a weird element that pops up near the wishlist count and fades away. Removing an item from the wishlist does the same thing including causing the wishlist to not respect pagination settings.

Figured out the weird element that pops up just says “Please wait…” and was squished by my CSS. The only problem that exist and still stands is that adding/removing an item from wishlist will cause wishlist pagination to break and load as if there wasn’t pagination. But perhaps this is not the fault of the total count AJAX.

• This reply was modified 7 years, 5 months ago by gavsiu.

After using it for a while, I noticed that at certain page widths, the logged in user name and search icon will show even if admin bar is supposedly hidden. I am now on 4.7.2.

Alright. Thanks.

Found the problem. BackWPup does not support ASCII passwords. Changing to alphanumeric solved the login problem.

[30-Dec-2013 23:47:09] 1. Try to send backup file to an FTP server …
[30-Dec-2013 23:47:09] Connected via explicit SSL-FTP to server: redacted.com:21
[30-Dec-2013 23:47:09] FTP client command: USER redacted
[30-Dec-2013 23:47:10] Undefined offset: 0
[30-Dec-2013 23:47:10] FTP server reply:
[30-Dec-2013 23:47:10] Undefined offset: 0
[30-Dec-2013 23:47:10] FTP client command: PASS *******
[30-Dec-2013 23:47:10] Undefined offset: 0
[30-Dec-2013 23:47:10] FTP server reply:
[30-Dec-2013 23:47:10] Undefined offset: 0
[30-Dec-2013 23:47:10] FTP client command: SYST
[30-Dec-2013 23:47:10] WARNING: ftp_systype(): Login incorrect.
[30-Dec-2013 23:47:10] ERROR: FTP server reply: Error getting SYSTYPE
[30-Dec-2013 23:47:10] ERROR: FTP Folder “BackWPup” cannot be created!
[30-Dec-2013 23:47:10] 2. Try to send backup file to an FTP server …
[30-Dec-2013 23:47:11] Connected via explicit SSL-FTP to server: redacted.com:21
[30-Dec-2013 23:47:11] FTP client command: USER redacted
[30-Dec-2013 23:47:12] Undefined offset: 0
[30-Dec-2013 23:47:12] FTP server reply:
[30-Dec-2013 23:47:12] Undefined offset: 0
[30-Dec-2013 23:47:12] FTP client command: PASS *******
[30-Dec-2013 23:47:12] Undefined offset: 0
[30-Dec-2013 23:47:12] FTP server reply:
[30-Dec-2013 23:47:12] Undefined offset: 0
[30-Dec-2013 23:47:12] FTP client command: SYST
[30-Dec-2013 23:47:12] WARNING: ftp_systype(): Login incorrect.
[30-Dec-2013 23:47:12] ERROR: FTP server reply: Error getting SYSTYPE
[30-Dec-2013 23:47:12] ERROR: FTP Folder “BackWPup” cannot be created!
[30-Dec-2013 23:47:12] 3. Try to send backup file to an FTP server …
[30-Dec-2013 23:47:12] Connected via explicit SSL-FTP to server: redacted.com:21
[30-Dec-2013 23:47:12] FTP client command: USER redacted
[30-Dec-2013 23:47:13] Undefined offset: 0
[30-Dec-2013 23:47:13] FTP server reply:
[30-Dec-2013 23:47:13] Undefined offset: 0
[30-Dec-2013 23:47:13] FTP client command: PASS *******
[30-Dec-2013 23:47:13] Undefined offset: 0
[30-Dec-2013 23:47:13] FTP server reply:
[30-Dec-2013 23:47:13] Undefined offset: 0
[30-Dec-2013 23:47:13] FTP client command: SYST
[30-Dec-2013 23:47:13] WARNING: ftp_systype(): Login incorrect.
[30-Dec-2013 23:47:13] ERROR: FTP server reply: Error getting SYSTYPE
[30-Dec-2013 23:47:13] ERROR: FTP Folder “BackWPup” cannot be created!
[30-Dec-2013 23:47:13] ERROR: Step aborted: too many attempts!
[30-Dec-2013 23:47:13] ERROR: Job has ended with errors in 11 seconds. You must resolve the errors for correct execution.

I can see in my console on the FTP server that the user has logged in, but when it tries to send the backup, the console also registers invalid login. I can log in to the FTP server the same way with WinSCP and create the folder manually, but this plugin throws a fit.

Forgot to mention it does successfully log in before this error.

I believe this issue may be caused by not being able to write to parent directory.

I’m going to keep the upload folder as wp-content/uploads and use htaccess to redirect /assets/ to wp-content/uploads.

I’m just going to use this:

function assets_path($fullpath) {
  $upload_dir = wp_upload_dir();
  $replaced_path = str_replace($upload_dir['baseurl'], '/assets', $fullpath);
  return $replaced_path;
}

and add a rewrite for /assets/ to /wp-content/uploads/

Didn’t seem to do anything. The url WordPress spits out should work. I even double checked with an FTP explorer. /assets/ is in the root and the images exist as was created by WordPress.

It’s not the author of this plugin. It’s the php app that they used.

https://code.google.com/p/minify/source/browse/min/lib/Minify/HTML.php#138

Anyone looking for an offline solution for jpegs, there is The JPEG Reducer. Like Smush.it, it uses jpegtran to optimize jpeg files. Basically, it’s just an interface for jpegtran for Windows. Tried a test image. They both seem to produce the exact same filesize in bytes.

https://home.arcor.de/shld/thejpegreducer/

For pngs, I use PNGGauntlet which, I believe, is a Windows interface for PNGOut (too lazy to check). Tried to Smush an optimized PNG image from PNGGauntlet and Smush.it couldn’t do anything more, so I believe it’s just as good if not better.

https://pnggauntlet.com/

Seemed like unnecessary code change that would break user themes. Disabled yet another feature of Jetpack because it’s causing problems for my website. Now I hand coded Twitter, Facebook, and Google+.