luckyfella73

Hi,

the repeater-field is part of the ACF-Pro version of the plugin. Since you have a license key, all you have to do is download the pro-version via your ACF account: https://www.advancedcustomfields.com/my-account/ and paste in your license key. This will unlock the pro features.

It is actually $ 149 /year for 10! websites – about $ 15 /year for one website. In my opinion this is absolutely worth the time you save by using it. Saving 1 hour pays for 5 years license cost (for me at least). If you buy the unlimited version for $ 250 you need to have 17 websites to get to costs of $ 15 for one website and every website on top of it makes it even cheaper.

Hi,

first of all thanks for your great plugin!

But I find it an issue as well that all other formfields are validated before clicking at the submit button. It’s just not common that you get validation error messages on all required fields just because you selected a radio button somewhere in the form. It just looks “ugly” to get plenty of red notices suddenly.

I’m using your plugin since years now and never faced that behavior – maybe I didn’t use radio buttons that much?

Edit:
Forgot to mention this: one radio is selected by default (in my case) so basically there is no need to fire a validation on change because you can’t deselect radio buttons – so why is the validation even of all other formfields triggered when just changing the radio selection? Maybe I’m just thinking wrong?

• This reply was modified 2 years, 4 months ago by luckyfella73.

I just had the same issue and found out that WPML (I have WPML version 4.3.12 installed) is not completely compatible with the 14.x version of YOAST SEO. Reverting YOAST SEO to version 13.5 solved this problem.

Hi Jules,

thanks for fixing that issue that fast! I installed version 1.7.1 and checked via VMWare IE11 – it worked fine.

Best regards

Hi Vladimir,
thank you for responding. In the meantime I found out that the plugin Photography Management didn’t allow custom roles to handle uploads sufficiently. In the meantime the plugin author added that feature after I did a request – so in case other users need to allow custom roles/ or build-in editor for Photography Management plugin:

// allow build-in editor:
// define in wp-config.php
if (!defined('PHMM_ALLOW_EDITORS')) {
	define('PHMM_ALLOW_EDITORS', true);
}

// call filter to allow custom roles (example):
add_filter('codeneric/phmm/user_can_administer', 'codeneric__phmm_user_can_administer' );

function codeneric__phmm_user_can_administer() {
	$user = wp_get_current_user();

	if ( in_array( 'your_custome_role_slugname', (array) $user->roles ) ) {
		// return TRUE to allow
		return true;
	}
}

Thanks and kind regards

@cag8f according to the plugin description the following shortcodes are build-in (at least up from version 1.0.3):
CF7_GET
CF7_POST
CF7_bloginfo
CF7_get_post_var
CF7_get_current_user

Up to now I didn’t use this plugin but I would watch out for all the listed keywords in combination with dynamictext dynamicname which seems to be part of all possible shortcode combinations. Just check out the description page yourself to be sure not to miss any of them:
https://www.ads-software.com/plugins/contact-form-7-dynamic-text-extension/

You could open the edit views of all contact-form-7 forms listed in the wordpress backend and check for the shortcode used by this plugin. If the shortcode is not used the plugin shouldn’d do anything. Just an idea – maybe there are better ways to go here.

@ashokrane
thanks for your feedback and nice you are going to release an update soon!

Hi,

I had the same error message and was able to fix it hopefully.
In plugins/arconix-faq/includes/class-gamajo-dashboard-glancer.php around line 123 modify the function like this:

protected function get_single_item( array $item ) {
	$num_posts = wp_count_posts( $item['type'] );
	$status = $item['status'];	// added this line
	$count = (int) $num_posts->$status;	// mofified this line

	if ( ! $count ) {
		return '';
	}

	$href  = $this->get_link_url( $item );
	$text  = number_format_i18n( $count ) . ' ' . $this->get_label( $item, $count );
	$text  = $this->maybe_link( $text, $href );

	return $this->get_markup( $text, $item['type'] );
}

I have PHP 7.0.12 running and WP 4.8.2

Can’t explain why it works or what was wrong exactly but maybe it is helpfull for somebody.

EDIT:
The author of class-gamajo-dashboard-glancer.php has fixed the error more elegant – of course ??
https://github.com/GaryJones/Gamajo-Dashboard-Glancer/blob/develop/class-gamajo-dashboard-glancer.php

Just replace line 123 with this:
$count = (int) $num_posts->{$item['status']};

• This reply was modified 7 years, 1 month ago by luckyfella73.
• This reply was modified 7 years, 1 month ago by luckyfella73.

I guess I found the git repository but it seems not to be up to date:
https://github.com/wp-plugins/sp-faq

Last update on WP plugins site is 3 weeks ago, last change at git 7 month ago..

Usualy I don’t like to suggest other plugin on pages that offer the same kind of plugin but in case you need an other nice faq plugin have a look here:
https://de.www.ads-software.com/plugins/arconix-faq/

works fine with foundation

Dear developer,

correct me if I’m wrong – I’d like to suggest to wrap the html code your plugin generates and set an unique id for the wrapper so you can define your “column” and “columns” etc css classes only used if inside the wrapper. It seems that your plugin can’t be used when your website is based on the foundation css framework (using the “column” class and other you are setting).

If you set “.columns” to 100% you get a conflict with foundations notation – lets say you want a 3 columns layout for tablets and bigger, you write:

<div calls="row">
<div class="small-12 medium-4 columns">Columns left</div>
<div class="small-12 medium-4 columns">Column center</div>
<div class="small-12 medium-4 columns">Column right</div>
</div>

That way no matter how many columns you want to get (foundation point of view) every div takes the full width due to your 100% for the css class “.columns”.

Or am I missing a setting?

Anyway thanks for sharing your work – best wishes

Hi,

strange but so often quite after posting a question you find the solution yourself…
Noticing the debug array in the Yoast setting pages I found the right array key,
stupid me…
In case someone else is lost finding this, here is how to get the meta description for custom post types archive by code:

$titles = get_option( 'wpseo_titles' );
$description = $titles['metadesc-ptarchive-YourPostTypeName'];

Hey Petra,

my WP throws 2 notices when doing a quickedit (posts). Here the notices (path shortened):

Notice: Undefined index: original_post_status in /.../plugins/search-everything/search-everything.php on line 919

Notice: Trying to get property of non-object in /.../plugins/search-everything/search-everything.php on line 931

My PHP Version: 5.5.14
WP Version: 4.3.1

Hope you find the error – best regards,
Luckyfella

Edit: It seems that the Input Data (when doing quickedit) is send by GET-method. Your Code line 919 is looking for $_POST vars. Mayby you can check if $_GET or $_POST index is available first?

After updating plugin the problem is fixed. The notice is saved as string in the texteditor field so remember to edit that and remove the notice there. Took me a while to find where the “PHP notice” is still comming from ??