megamurmulis

Page link: https://www.ads-software.com/plugins/contact-form-7/advanced/
Direct link: https://downloads.www.ads-software.com/plugin/contact-form-7.5.6.4.zip

Update v3.8.1 confirmed to work ok..
(I guess was due get_settings being called in __construct() while class instanced on init – thus pre plugins_loaded call)

Sounds like same issue as this:
https://www.ads-software.com/support/topic/big-log-files-fatal-error-in-backend-add-log-purge/

Latest update (v1.8.27) seems to improve things (less memory required for log file reading)

If you still experience problems:
a) you can delete big log files manually from: /wp-content/uploads/sucuri/,
b) or use that plugin to delete them automatically every week..

For now – something like this should help:
https://github.com/megamurmulis/sucuri-log-cleanup (use zip from Release page)
Can be deployed & installed via IWP – runs every 7 days, check via admin_init..

This..
At the moment forced to add lots of rules in email client to automatically delete such emails..

Tried various error situations – seems many not handled (not showing anything, gif just keeps spinning)..

Enter bad card: 4000000000003220

400/Bad Request  https://api.stripe.com/v1/payment_methods
Response: {"error": {"code": "card_declined",
"doc_url": "https://stripe.com/docs/error-codes/card-declined",
"message": "Your card was declined. Your request was in live mode, but used a known test card.", "param": "", "type": "invalid_request_error"}}

=> should show some error messages to user..
—
– top line too low in fieldset – maybe add:
.ds-element.in-form fieldset legend{top: -8px;}
—

Problem: some files are in incorrect path: /analyst/analyst/ = should have been just one folder..

Fix:
1. Navigte on FTP to: /wp-content/plugins/ultimate-social-media-plus/analyst/analyst/
2. Move the contents (files and folders) to the parent folder:
So they are in: /ultimate-social-media-plus/analyst/*
(as include looks for it there: require_once 'analyst/main.php'; )
—
<b>Resolved in:</b> v3.2.1

• This reply was modified 5 years, 7 months ago by megamurmulis. Reason: clearer phrasing
• This reply was modified 5 years, 7 months ago by megamurmulis.

v4.0.1 = working ok..

—
Typo in plugin (“shortcoder.php”) description text: “exceuted” => “executed”..

@rajatgavri – version v4.0.1 with the fix isn’t out yet..
Until then – You can either apply fix manually / disable plugin (via FTP)..

Note: If your site is down due “Fatal Error” = you will need FTP access to edit that line of code..

Version 4.0 causes Fatal Error (or Error 500) on PHP <5.4:
(due empty(): Can’t use function return value in write context)

Fix:

FILE:    shortcoder/admin/sc-admin.php
LINE:    248
	public static function save_shortcode(){
-		if( empty( trim( $p[ 'sc_name' ] ) ) ){
+		if( ! trim( $p[ 'sc_name' ] ) ){

Not true how? You can easily verify this yourself..

When using newer CF7 (like 4.3.x) on older WP (like v3.9.9) – you will get message: Contact Form 7 4.3.1 requires WordPress 4.2 or higher. Please update WordPress first.

Note:
– create, edit, display form on frontend = all working ok;
– but when form is submitted – AJAX POST request will fail.

What happens next depends on your server config:
You either get a non-descriptic Error 500 or if you have Debug/Error logging enabled – you can see actual error instead of Error 500:

Fatal error:  Call to undefined function wp_json_encode() in wp-content/plugins
/contact-form-7/includes/controller.php on line 97

..

Solution:
If updating to WP 4.1+ is not possible then:
a) use older CF7 version;
b) or you can just add missing functions using a fix plugin:

You will need to copy 3 functions from: wordpress-4.1.8.zip/wordpress/wp-includes/functions.php

wp_json_encode
_wp_json_sanity_check
_wp_json_convert_string

Sample plugin:
https://pastebin.com/urhmsP9k

Error 500 = server side php error, not JS..

Note that recent CF7 versions will throw Error 500 if you use them with older WP versions ( <= WP v4.2 ).
You will need to install older version in that case..

Hmm, I see that v3.0.0 uses:

.ui-state-default .ui-icon:before {
	content: "\e259";
.ui-state-active .ui-icon:before {
	content: "\e260";
	font-family: 'Glyphicons Halflings';

1. those char codes are from halflings font – if Glyphicons is loaded will show incorrect glyphs (see https://glyphicons.com/ )

2. Not every WP theme uses bootstrap / or loads Halflings font.
= In such cases will just show “empty box” / invalid glyph box.

So – you must loads Halflings font manually / use img fallback.

Note: WP 3.8+ has built-in font dashicons ( https://developer.www.ads-software.com/resource/dashicons/#arrow-down-alt2 )

.ui-state-default .ui-icon:before {
	content: "\f347"; /* dashicons-arrow-down-alt2 */
}
.ui-state-active .ui-icon:before {
	content: "\f343"; /* dashicons-arrow-up-alt2 */
}
.ui-state-default .ui-icon:before,
.ui-state-default .ui-icon:after {
	font-family: 'dashicons';
}

~But not available in older WP version, so not that good for compatibility..

You can use echo get_views(get_the_ID()); for displaying only without updating counter..

Note that if you do not use echo_views – then you will need to manually call update_views(get_the_ID()); in your single post page..

– Yes, I allready noted the problem with index.php vs. index.html..

– As noted – WP includes this file in 3+ places (and some themes/plugins sometimes follow this suite) = but not relevant..

– Also i’m not relaying on this for any security / to prevent directory listing = whole point feedback is about index.php being non-empty..

Now that we finally got those assumptions out of the way:
~ well, some SVN indeed used to have problems with 0B files;
~ but not aware of any webserver that has problems with 0B index document (not that it matters, since not using for redirect / or outputting anything).

Anyway – then a compromise suggestion:
– Use index.php with only opening tag: <?php.
(only 5 bytes – too small for anything, then content become irrelevant)