bswan

I second this on scheduling, however the issue I also see as fairly large is how it deals when you take a backup with W3TC.

WP current 3.81
Clean Install
No error
No screen shot it just resets to nothing.

Right, because PageLines and Google Analytics breaking your application makes your application valid.

I went back to “Login with Ajax” –

I am also experienced “Undefined” in red above the login screen, when nothing is at all wrong with the login credentials.

FTP deleted it the first time, when I tried reinstalling that is when your plugin bricked my website and I had to reinstall WordPress because when I tried deleting again, your plugin files were no longer there yet the error did remain for several minutes even after refreshing and restarting my FileZilla. You can passive aggressively use quotations after this response as well.

To answer your question more throughly than Esmi, the answer to your inquiry is due to the HTTP error you received could well be syntactic error in your pasting. If double checking that does not resolve your issue, follow this further reading, as well as the exact question closed out 4 years ago https://www.ads-software.com/support/topic/http-403-error?replies=5

https://en.wikipedia.org/wiki/HTTP_403

https://pcsupport.about.com/od/findbyerrormessage/a/403error.htm

HTTP Error 403 – Forbidden

Generally. the HTTP error 403 – Forbidden means that access to the file/folder you are trying to open has been denied, either on purpose or due to a misconfiguration.

If you suspect that only your access is blocked, try a web proxy to hide your identity.

If you are the site administrator check the webserver’s error log when troubleshooting. Most web hosting control panels give access to such a tool. In cPanel, it is called Error log. Check the manual for your webserver if you don’t have a control panel.

In the error log you will see a list of the last error messages generated by your website. In this list you will find detailed information about each error including: the date and time of the error, some information about the client receiving the error, description of the error and information about which folder or file on your account is generating the error.
Here are some examples of the most common errors and how to fix them:
[Thu Apr 19 01:46:56 2007] [error] [client 127.0.0.45] client denied by server configuration: /home/user/public_html/file.php
This error message may be received when the access of certain IPs to certain files/folders/websites is forbidden by a rule added in the .htaccess file. If you do not want to deny access to this IP you should make sure your .htaccess files do not contain such rules. In order to check if such rules are added to your website you should open the .htaccess file in the folder that generates the error and search for a line such as:

deny from 127.0.0.45
– this rule denies access from a particular IP, in this case 127.0.0.45

deny from all
– this rule denies access from all IPs

If you find such a line you should delete it and save the change. After that the client with this IP should be able to access the files in the folder and will not receive the “403 forbidden” error.
[Thu Apr 19 02:13:24 2007] [error] [client 127.0.0.76] Directory index forbidden by rule: /home/user/public_html/
Such error message will be displayed when a user tries to open a directory which has no index file and at the same time the Indexes option for this directory is turned off. In order to avoid this from happening, you should make sure that the .htaccess file within the directory which displays this error does not contain a line like the one below:
Options -Indexes

IMPORTANT: If you are not sure how to edit your .htaccess file, please refer to the “Editing a file” section of the File Manager Article from the SiteGround web hosting cPanel tutorial.

If you cannot find the reason for the 403 error yourself, you may ask your host for assistance. SiteGround provides the best web hosting and such requests are handled with ease.

https://kb.siteground.com/article/403_Forbidden_error.html

This moderator should honestly provide better feedback than “yeah you’re a cry baby mine works fine” –

Am I allowed to trash moderators or recommend their downgrade @ esmi?

This is due to W3TC and the core developers not working closely together, or having a disconnect prior to release. You must remove your W3TC files (not simply just the plugin folder, you have to delete the cache content as well, as you will see errors on your main page. Then you must snag a fresh functions.php from the 3.4.1 release and drop it back in via FTP.

This is about a bad a release as Visual Studio SP1 hahah… I guess nobody at core got the memo that a million people use w3tc

oops

1. You’re wrong, and 2. You have no idea what theme I’m talking about, and 3. You aren’t a moderator, so why are you responding like one?