kotpesgmail.com
Forum Replies Created
-
Line 26:
if (PLL()->model->get_post_language($hit->ID)->slug == ICL_LANGUAGE_CODE) {
but error still says the same. Any guesses why it is so?Hm, I’m using composer to manage plugins, it ((https://wpackagist.org/search?q=relevanssi&type=any&search=) actually shows 3.5.4 as latest and 3.5.3 on WordPress plugins directory.
Hey, thanks for getting back. Still getting the error even on latest version of Relevanssi:
Notice: get_post_language was called incorrectly in /srv/www/site.dev/current/web/app/plugins/relevanssi/lib/common.php on line 26: the call to $polylang->model->get_post_language() has been deprecated in Polylang 1.8, use PLL()->model->post->get_language() instead. Error handler in /srv/www/site.dev/current/web/app/plugins/polylang/include/model.php on line 595 Notice: get_post_language was called incorrectly in /srv/www/site.dev/current/web/app/plugins/relevanssi/lib/common.php on line 26: the call to $polylang->model->get_post_language() has been deprecated in Polylang 1.8, use PLL()->model->post->get_language() instead. Error handler in /srv/www/site.dev/current/web/app/plugins/polylang/include/model.php on line 595 Warning: Cannot modify header information - headers already sent by (output started at /srv/www/site.dev/current/web/app/plugins/polylang/include/model.php:595) in /srv/www/site.dev/current/web/wp/wp-includes/pluggable.php on line 1171Hey, Mikko, having same issue. Is there a quick work around (besides changing /lib/common.php)?
Forum: Plugins
In reply to: [Account Engagement] wp-load.phpyeah, it worked, but I don’t think I should go on production like that
Forum: Plugins
In reply to: [Account Engagement] wp-load.phpOk, this is what I get right now:
Warning: file_exists(): open_basedir restriction in effect. File(/srv/wp-load.php) is not within the allowed path(s): (/srv/www/:/tmp:/srv/www/affecto.dev/current/web/app/plugins/pardot/includes/) in /srv/www/affecto.dev/current/web/app/plugins/pardot/includes/pardot-wp-loader.php on line 22 Warning: file_exists(): open_basedir restriction in effect. File(/srv/wp-load.php) is not within the allowed path(s): (/srv/www/:/tmp:/srv/www/affecto.dev/current/web/app/plugins/pardot/includes/) in) in /srv/www/affecto.dev/current/web/app/plugins/pardot/includes/pardot-wp-loader.php on line 30Which is I know wrong (the open_basedir), but the problem is in
File(/srv/wp-load.php)Forum: Plugins
In reply to: [Account Engagement] wp-load.phpAdd
/srv/www/affecto.dev/current/web/app/plugins/pardot/includes/to my session.save_path, correct?Forum: Plugins
In reply to: [Account Engagement] wp-load.phpI get exactly same error. Im concerned about this part of the error message
File(/srv/wp-load.php)this is not the correct pathForum: Plugins
In reply to: [Account Engagement] wp-load.phpYes, sir
Forum: Plugins
In reply to: [Account Engagement] wp-load.phpI don’t understand why it says
File(/srv/wp-load.php)if my wp-load.php is in/srv/www/affecto.dev/current/web/wp
session.save_path = /tmpThis is how my session.save_path looks likeI suggest you’d make a note somewhere on plugin’s page that states that. Because after checking out this page http://cfdbplugin.com/?page_id=459 and seeing the screenshots I was under impression that plugin lets me change name of the fields including for future submissions.
Otherwise, great plugin! Keep it up)Yes, it works, but it means that I don’t need the plugin itself because I can’t permanently rename column’s names using the interface, right?
Form Name: Vendor Form
Fields:
FirstName -> First Name
LastName -> Last Name
PhoneNmuber -> Phone NumberBut in there I can’t give fields name that consists of two words with break between them. And this is why I need the plugin at the first place – to turn fields like FirstName to First Name (with space)
Form definition in Contact Form 7 plugin you mean?