thezedt

Hi,

This error is most likely caused by the notifications table creation query failing during the EDD update on older versions of MySQL (under 5.6? my test system is 5.5.68) due to CURRENT_TIMESTAMP() being an unsupported default value for the date_created and date_updated columns.

The notifications functionality looks introduced in EDD 2.11.4.

To complicate matters, changing the columns types to timestamp is insufficient, since older MySQL will now complain with:
Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

Since I see EDD does set default values in the code for these two columns, I removed the default SQL value for both columns and that allowed me to manually resolve the error by creating the table manually with:

CREATE TABLE __TABLENAME__ (
	    id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT,
	    remote_id bigint(20) UNSIGNED DEFAULT NULL,
	    title text NOT NULL,
	    content longtext NOT NULL,
	    buttons longtext DEFAULT NULL,
	    type varchar(64) NOT NULL,
	    conditions longtext DEFAULT NULL,
	    start datetime DEFAULT NULL,
	    end datetime DEFAULT NULL,
	    dismissed tinyint(1) UNSIGNED NOT NULL DEFAULT 0,
	    date_created timestamp NOT NULL,
	    date_updated timestamp NOT NULL,
	    PRIMARY KEY (id),
	    KEY dismissed_start_end (dismissed, start, end)
		) DEFAULT CHARACTER SET __$wpdb->charset__ COLLATE __$wpdb->collate__;

Update the table name, charset and collation with those valid on your server.

I can’t say if the table structure change has any effect on the dashboard functionality (I haven’t noticed anything terribly broken so far, though).

Hi,

?The “camera” icons are there as failsafe in case the featured boxes have no images. Otherwise they are overlapped by the featured images and not visible. Are your featured images semi-transparent?

You can remove the icons with a bit of CSS:

?body .lp-box-image::before {
    display: none;
}?

The forum doesn’t accept images, but you can see the respective option and options panel here: https://imgur.com/a/O7Td936

Hi,

By default the theme uses placeholders in the comment form, which can hide extra custom fields added by plugins. That can easily be resolved by changing the Comment Field Label option to the Labels value, from the theme’s Post Information > Comments options panel.

It’s worthy to note that things will also fail if the /recaptcha/api.js script is loaded deferred (maybe due to some optimization plugin or technique).
Wasted one hour scratching my head before I noticed this ??

I don’t see the direct relation between features and quality.

Anima has all the features our other themes have, however it has to have its unique look and design, which don’t quite work with individual post backgrounds.

Not looking the same as others themes shouldn’t be a minus.

The theme has 6 widget areas: header, footer, sidebar left, sidebar right, above content and below content. There is no ‘top’ widget area in Fluida.

You left a review 36 hours after posting in the support forums with a problem that is not sufficiently explained and cannot be seen (since it’s in the dashboard).

You CANNOT punish the theme with a bad review for not receiving free support for a free product in such a limited timeframe.
You are still using the theme on your site. If it was such a bad experience why didn’t you switch to a different one?

The theme has 6 widget areas: header, footer, sidebar left, sidebar right, above content and below content. There is no ‘top’ widget area in Fluida.

You posted this review 36 hours after posting in the support forums with a problem that is not sufficiently explained and cannot be seen (since it’s in the dashboard).

You CANNOT punish the theme with a bad review for not receiving free support for a free product in such a limited timeframe.
You are still using the theme on your site. If it was such a bad experience why didn’t you switch to a different one?

Unless something serious changes in WordPress’ dashboard functionality, the plugin does not need updates to maintain compatibility with newer WordPress versions.

We’ll bump the ‘tested up to’ version for peace of mind.

Thanks for pointing this out. It is fixed in today’s update.

Thanks for pointing this out. It is fixed in today’s update.

Yup, 1.1.3 was indeed broken (due to an incomplete file).
We’ve just published 1.1.4 to correct this. Sorry about the issue.

Place the files in wp-content/languages/themes/

If you’re placing them in fluida/languages, they should be named simply cs_CZ.mo and cs_CZ.po (but they’ll get deleted at the next theme update).

Fluida doesn’t visibly display the site tagline (for now) – it is only used as the title’s hover hint.

That widget area is not designed to have a background color – it’s mostly intended for widgets which come with their own styling.