Webartisan
Forum Replies Created
-
@cais – Thanks for your reply, I’ll answer on the other topic.
Thank You.
I must add something that I realized only now and that maybe could have a role in the issue.
Before upgrading to 2.0.66.37 we were facing a problem related to NextGEN in the website (total blank pages both in front- and back office), so I changed the folder name to plugins/DEACT_nextgen-gallery in order to temporarily get access to back office, then I changed the folder’s name back and made the upgrade.
Forum: Plugins
In reply to: [Easy Contact Forms] How to add BCC?I’m also interested in this. It would be great if addresses in “Mailing List” could be checked as “CC” or “BCC”.
Have the same problem here.
As far as I can figure out it must be something related to the “Hide login area” section of BWP Security (or iThemes security, how it’s called now).
I’ve always used that option to change the /wp-login and /wp-admin and make a little harder to find the access to backoffice.If I temporarily disable the “Hide backend feature” the calls to admin-ajax.php work again.
I suppose that is because when you don’t have hide-backend enabled the ajax url is typically http://www.yoursitename.com/wp-admin/admin-ajax.php, but when you enabled it (and you’re not already logged in) every calls to a page containing /wp-admin/ will generate an error.Personnally I’m going to downgrade to the last working version and check the progress of the fixing progresss before upgrading to a new version.
Solution suggested by poltadaalu worked for me too.
- With a FTP client go to the wp-filebase folder in your plugins folder (normally: wp-content/plugins/wp-filebase/);
- Download the file wpfb-ajax.php and open it with a text editor;
- Go to line 9 and put // (two slashes) before @ob_end_clean(). This means “commenting line nr9 out”;
- Save the file and upload it back to the original folder.
Hello,
I’m still struggling with this. I understand that maybe I should add my fields to theglobal $wpcf7_contact_formin my (shortcode)function but I can’t figure out how. Perhaps plugin’s author could give a hint (if interested). Thank you.Forum: Plugins
In reply to: [Custom Content Type Manager] CCTM and cookieless static contentThank You. I supposed that was something related to the change of options.
I managed to solve by reading to the FAQ and using Export/Import Tool and now it’s working as expected.I agree with your opionion about storing/retrieving of serialized data on WP and I’ll take a deeper look at your wiki about CustomFieldsDataStructure.
Ok, thank you. Just sent you the files.
Please update french translation as the problem with link not properly closing brokes the “Add new category” section.
One can not enter a form field (i.e. category name) because it’s like clicking on a big “Add new category” link again and again.I updated my copy but at the next upgrade it’s going to be still reversed to previous version.
Where can I send the correct version of wpfb-fr_FR.po?
Excuse me, the post has (obviously) been truncated where i put parts of html code.
The problem is in link closing. “lower-than slash SPACE a greater-than” instead of “lower-than slash a greater-than”.
It recurs two times in the .po file.Hi,
I don’t know if such a function is expected to be included in future versions of ThreeWP Activity Monitor (though it would change its main purpouses of simple reporting, IMHO) but currenlty I’m using also “Limit Login Attempts” plugin to acccomplish it.
http://wordpress.org/extend/plugins/limit-login-attempts/Have the same problem in a similar context.
I could try other captcha plugins but what I appreciate in Really Simple Captcha is the small size, ideal in places such as footer forms.Thank you,
MarcoI added the issue as a feature request (though not so important) with a small explication of what qT does.
Thank you.Hi, pardon my english. Maybe “overridden” is not the correct term and I didn’t mean to say that qTranslate does it (actually I don’t really know what it does 🙂 ). Apologize me for saying that.
What I wanted to express was that just by adding some __() (as you wrote in the issue report) for some important variables that normally are not supposed to be translated, such as post_title, can prevent these little problems.
Sorry, I forgot to mention that the
customized_hierarchical_post_types()function is in custom-content-type-manager/includes/StandardizedCustomFields.php file.