MrsJessicaSimpson

Thanks for the update: didn’t know, and I’m definitely having a look at it.

Cheers again, ..

One thing threw me completely, so much so – that I fingered that the plugin didn’t work at all, and it was:-

Automatic Updates

These options will enable or disable automatic updates (background updates) of certain parts of WordPress. Select Custom for more flexibility. Leave as Default for normal WordPress behavior

[Default[ [On] [Off] [Custom]

So you figure default is what you want: < NOT! > – It’s …

[ ON. ] Meaning that Automatic updates are … wait for it, but — on, to be run automatically.

As I say: the out of the box ( install, update? ) – Doesn’t enable the plug-in. It might not be your problem, but since I found that toggle: then the Plug-in on my web site worked like a charm.

Hope it helps.

Curiosity eminently **RESOLVED**: and also educated at the same time, but to a degree much more that perfect, more like superlative.

Thank you.

First thing is that by default there is no
define(‘AUTOMATIC_UPDATER_DISABLED’, true);
in wp-config.php file. So by default, you are not need to edit wp-config.php file.

Never knew any of that, learning all the time and thanks for sharing.

– Maybe you could mention (that fascinating fact) somewhere on your WiKi to basically stop old women like me having a melt down, and fretting, and a nervous break down to boot, whilst also losing a good night’s sleep, and not to mention my will to live.

Would I say that that exercise stressed me out? – Yup! – Just a bit, but it’s over and now I’m looking forward to my first eMail telling me it’s all done and dusted back at base.

BTW – Your Plugin’s interface is very easy to understand and straight forward, (five stars), and in saying that: then I don’t see why some old web foggies declared otherwise. In fact, the entire thing so far is 5 stars.

UPDATES? – Yup did that before I started, ain’t I a good girl, but even that didn’t stop me stressing.

Anyway: many thanks for your correspondence on this matter, it’s good to type.

My goodness, but that gets complicated real quick.

OK : to remove that error above? – If that’s what it was.

I re-edited the WP-CONFIG.PHP file and took out that line about AUTOMATIC UPDATES.

– But, before I did that: I found out that you have to change the WP-CONFIG.PHP file permissions to 700 [r/w/e] by owner, from it’s default of 400, which is read only by the owner ie: [r/x/x/]

*URGENT WARNING: DON’T FORGET TO CHANGE IT BACK TO 400.*

I managed to crash the ftp-program in attempting to edit a protected file with transfer errors all over the place.

*URGENT WARNING: DON’T FORGET TO CHANGE IT BACK TO 400.*

Finally uploading the modified system file, and then refreshing my site: I fully expected the worse, and to be prudent; I kept the ftp-program file open and ready to reset everything. I’ve crashed out my site big time before now, and know all the tricks of the trade; like keeping everything open and live whilst updating, so you at least have a chance to get the recovery underway.

(—)

To my intense relief and delight the modification didn’t smash my site, the red TAB warning disappeared, and the updater program says ( nothing! ) – So I still don’t know if it will work or not, but the warnings have gone.

The above information has been added to help anyone else wondering what will happen.

BTW – developer: your WiKi saying, …

If you find the line define(‘AUTOMATIC_UPDATER_DISABLED’, true);,
remove it and try the Force Updates button in the Advanced section of the Easy Updates Manager settings.

If Force Updates works, then the plugin/WordPress will check for automatic updates every twelve hours from then on out.

After reading the above, I was still none the wiser on whether I should/could/or even needed to take such draconian action on my root directory.

– But I have done: and my site seems to be functioning, but I’m a bag of nerves in re-editing that system file.

Perhaps a walk through might be an option, especially covering file permissions, – and also what this powerful file actually does. Looking through it very carefully: I realised that I could have ripped my database link from my site with the casual flick of a wayward finger.

Really need to have a rest now and put my feet up, this old girl’s had it.

P.S – URGENT WARNING: DON’T FORGET TO CHANGE THE FILE PERMISSIONS OF THE WP-CONFIG.PHP BACK TO 400, – Because it seems that this file can be hacked, and once a hacker gets hold of it: then your site is doooooomed to become a slave-Bot for spammers, or worse; perhaps it will become involved in the black art of re-mailing top secrets, and you’ll only know about it: when someone knocks on your door at five in the morning with flashing blue lights behind them.

Nothing to do with updates, but everything to do with getting the updater to work.

Feet up, and now snoring loudly.

Hi Ben,

This subject has fascinated me: so much so, that I began digging, because I also need another Icon not supported, but mine is for (feedbooks) and I’m not asking for it to be included as I’ve used the QQ Penguin Icon, or whatever that Chinese thing is.

Anyway, going through your Icon library from Font Awesome, – I’ve found a book one called fp-book that looked quite good. Altered my (fat Chinese penguin) using the browser Inspector, and it really does fit the bill.

That Icon could be a good generic editing Icon for us awkward blighters.

Book writer contact links for example are feedbooks and goodreads and wattpad to name just three, more book sites here, and I have accounts on a couple of them.

Tried to include the Book Icon on my site, and crashed it, – (Badly!) – But I was still logged in with FileZilla, so I just changed the customiser.php file back to the old one.

But from that, I realised that’s it’s not going to be *that* easy.

Now, I’m not asking you to implement that Book Icon, but perhaps you could just keep the idea on the back burner, for perhaps a future feature?

Cheers from Jessica.

Hey there, and thanks chaps!

– I didn’t expect anyone to respond to another Plugin’s condition here, and your suggestions *WORKED* – means that I don’t have to put any extra CSS into my main Home page, and that saved me a ton of extra work I can tell you.

Many thanks again, RGDS – Jessica.

CRACKED IT.

– How too add a blank, (un-clickable), invisible menu separator on a vertical menu: in other words, a spacer.

{ And in twelve easy steps: AA you say. }

1.) – Goto the WordPress Customize under Appearance.?
2.) – Find and open the [ Menus Section ].
3.) – Move to the bottom of your Menu list: locate [ Custom Links ], – and then open it.
4.) – In the [ Menu Widget ] you’ll find.

URL — https://
Link Text — [ it’s empty BTW ]

5.) – Just put a ‘#’ in each.
{ Don’t include the quotes, just put the hash # word in. }

6.) – Then select and click -> [ Add to Menu ].
7.) – Move the new Menu Item to where you want it in your Menu List.
{ This will be where you want your vertical spacer to appear. }

8.) – Open up the ‘#’ Menu Item by clicking on the ( Small Triangle ).
9.) – Find the text box section called [ CSS Classes ] and then put the word ‘myspacer’ into it.
{ Don’t include the quotes, just put the word myspacer in. }

10.) – Now close the Menu Item by clicking on that ( Top Triangle ) again.
{ Where you want the separator on your sites menu, you should now see a ‘#’ : no quotes BTW. }

11.) – Still in [ Customize ], goto the section at the bottom called [ Additional CSS ], then simply copy and paste the CSS code below into it.

/* menu item killer */
.myspacer {
pointer-events: none;
cursor: default;
visibility: hidden;
}

{ As soon as you’ve finished copying it in: your ‘#’ Menu Item, (no quotes), will have vanished, and you will now have an invisible vertical separator in your Menus. }

12.) – Click [ PUBLISH ] at the top of [ Customize ].
{ Hopefully: well done, as you’ve now finished the twelve step AA plan. }

13.) – A Baker’s Dozen : Want another separator?
– Simply make a new Custom Links Menu, and call it #2 or whatever.
– And then in it’s CSS Classes text-box, simply add the word ‘myspacer’ as you did in the first example.
– You now have another vertical separator.

Ben, an awful lot of people ask this basic question, but no one ever seems to resolve it: not without the question getting real complicated in selection the correct .iL menu item using CSS inspectors, but it’s not necessary.

Above is a generic resolution: complete, and succinct, and it might even draw in some new customers to your superb WordPress sites.

Hope it helps, Jessica.

Thank you very much for that snippet.

As a result I’ve been busy digesting that code, and then whizzing round the web matching it up: really need a good primer.

Many thanks again.

Case closed.

*Without* changing the subject.

Downloading update from https://downloads.www.ads-software.com/release/wordpress-4.8.1-partial-0.zip…

Download failed.: The checksum of the file (d41d8cd98f00b204e9800998ecf8427e) does not match the expected checksum value (93f5b9e6f0e24e245899165c6701f222).

Installation Failed

I have the exact same issue: now it’s all well and good saying do a manual install, and reading the instructions gives me the goosebumps, and yes! – At some point when I have half a day to spare, I’ll give it a go, but the question remains: why did the installation fail originally?

Rider: I know you work hard to provide this platform, and it’s all free of charge, and I know you are proud of what you do here, but when this happens: you chaps get really uptight, as in the above response to check-sums.

– Something wrong happened here, and no one is pointing fingers, but a manual update of your site isn’t to be taken lightly. Perhaps one of you wizards could look into it at sometime, and (honestly:) tell us what happened here.

BTW – My other two sites updated without a hitch, but the one with the subdomain didn’t. This extra information (off topic), may help you track down the issue that caused my, robnicholson: and mhardin1369 problems.

Many thanks for reading, Jessica.

Thanks will give it a go!

I also, am not impressed with this foolish upgrade (down grade): It adds nothing to the functionality of this fine product.

It may be produced by volunteers, but someone; at some point : Said lets release it. [moderated]

Solutions to the width issue, and widgets not fitting across the screen.

1.) WP Admin Classic: Works well : Even donated, but it slooooowwwws the admin side right down. No doubt it will get sorted in time, and is a brave attempt.

2.) Admin Classic Borders.

Plugin Blurb:-
Starting with the MP6 plugin, and by default in WordPress 3.8, the admin backend has been flattened. This plugin restores classic (3D) borders.
Version 1.3 | By Andy Mercer.

Now it doesn’t reduce the fonts on the left hand side, but it does smooth out the huge spaces between the menus. You can reduce the wasted spaces : Introduced for fat fingers on Mobiles.
— Who runs their web site, from their mobile? — Dunno’

Handy options of Admin Classic Borders you might like:

Border Type. [none]

Select which type of border you’d like. Options are light, dark, and 3D (both). Default is 3D.

Restore 28px Admin Bar? [y]

The Admin Bar had a height of 28px until WP 3.8. 3.8 increased the height to 32px. While not a large change, many themes use this number when absolutely positioning elements, and many of said themes haven’t been updated to check for the new height. This will restore the classic (28px) height.

– Both options make a big difference.

Not perfect, but at least you have that much more control over the over all look and feel of the admin dash-board.

Developers of word-press please note, you cannot treat users like this. This foolish, ‘mobile-ready-upgrade’ : Completely breaks the trust you’ve developed with the community over the years.

— I wish you well with the next one.

Rgds – Jessica.

Don’t know why your getting so pissy?

Also the error you’re describing is a little illogical… If I delete .htaccess with WP in a folder off root, all that happens is my URLs break. I can still see the front page, log in, etc etc. As soon as I resave permalinks, it comes back.

If my .htaccess is deleted, or modified; then my web site does break.

The .htaccess file was modified by the installer on Friday. The file date was changed by it. I’m sure that none of my plugins did it. The site was working prior to the attempted update.
– It’s now working again. For my part, this response is irrelevant.

I’m using standard plugins, and I have them installed on all my sites.

They are:-

Akismet.

All in one Favicon

Conditional CAPTCHA for WordPress.

Custom Meta Widget.

Google Calendar Events.

Hupso Share Buttons for Twitter, Facebook & Google+

Lock Out.

Weaver II Theme Extras.

WP Multibyte Patch.

Select WP Updates Notifier.

WP User Avatar.

As I say, I’ve got it all working again. I hope you can make use of this information, and do find a link between them; and the installer.

Your attitude over this, is beginning to take on tones of hysteria.
For my part, I will now cease all communications with you over the matter, and have [de-ticked] the follow up link on this post.

RGDS:

WordPress does not delete the .htaccess ever.

It did, unfortunately.

I rebuilt it, and my site is now working as it should.
BTW: I went through all the options of renaming the plugins folder, and flushing the cache, also used another Browser.
… Didn’t do any good.

The Install did wipe my .htaccess, and without it, my web site went into a recursive deep hole. It was because I kept my WordPress files in a folder/directory : off the root folder/directory.

Mines working now, don’t know about ‘londonnet,’ but his/her fault was the same as mine. And I’ve seen this situation arise in the past.
… Very weird!

RGDS:

Solution:-

Put my .htaccess back, as below.

RewriteEngine On
RewriteRule ^(.*)$ https://www.gb-dl.co.uk/wd/$1 [L,R=301]

Found a backup of the .htaccess file, that used to reside in my /wd directory. If you’ll remember, the installer left it empty.
– It now looks like.

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wd/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wd/index.php [L]
</IfModule>

# END WordPress

My site is held on the folder/directory called /wd

– Should you also be suffering the same sort of issues I encountered after running the 3.7 update/installer. Then consider the solution I’ve outlined above as a means of relieving your stress.

Hope it helps.

– Praise be the ORI.