biswajeet

The is_admin is a boolean function generally used to identify WP front end or admin end. But it is not working accordingly with wp ajax environment. More clearly you can’t detect front end request. Within wp ajax environment it always remains true no matter if you are requesting it from the front end.

Please check it out.

What will be the purpose of the order form you were trying to build?
What action will be taken on form submitted? Will the form data need to be stored in DB or simply to send mail?

One thing to mind is that you can’t pre fill any CF7 field with data associated from product info. Additionally, you can’t extend the CF7 form with custom fields from outside simply like you assumed as above.

There might required several different meta tags related to different service integration & purposes – for example: adding FaceBook like/share/recommendation, Geo location integration, etc…

Now with such situation, you have to installed plugins for each small small purpose which is not the best way to go.

I personally don’t like to install plugins for each small task. I have previously used meta tag manager but it results performance degrade with AIOSEOP. So, I discontinued meta tag manager and hard coded the custom metas in the header.

thanks.

You are looking for a specific feature and that is not what the CF7 is for. I have seen many people wants their specific feature sets over CF7 which comes as a natural tendency due ease of use in creating form, fields etc. But the internal functioning of CF7 is to simply send mail and nothing else. It doesn’t maintain any db tables to hold all those data. So, for all custom features over CF7 is to implement additional module extension or to implement custom modules as per usage requirement.

Thanks for the update info…
I will check it.

All right, I have found the problem. Its because of the black slash character in JS object aioseopadmin for pluginPath property. I am using windows and Xampp as development environment and that property comes out as
pluginPath: "M:\xampp\htdocs\wptest\wp-content\plugins\all-in-one-seo-pack/"

I just comment that property and it works. So, I think this problem doesn’t arise other than windows.

Better use wp_script_localization for JS object output which handle such situation nicely.

The error is on quickedit_functions.js on line 7

ReferenceError: aioseopadmin is not defined error source line:	

...<img src="' + aioseopadmin.imgUrl+'accept.png" border="0" alt="" title="'+meta+'...

For second part suggestion with the reference above what actually I meant to say is simply to make exclude checkbox field depends on noindex or nofollow such that selecting any one of them auto select exclude checkbox. So, this makes the perfect logic that with noindex or nofollow set on it will be automatically excluded from the sitemap.

But why do you want to remove that button? Its come in handy when flushing caches!

Anyway, if you want to hide the button then try css option.

The error you are getting is due to another plugin which tries to modify the header. Have you got the same warning when you are already logged in? Check it out.

For css and js files you need mod_deflate to be enabled by your hosting provider. At present page loading time is very crucial for getting good rank in google as well from the visitors side too.

Currently, Most of the web hosting company have high charges while only a few of them provide support for mod_deflate compression. Be sure to ask regarding compression whenever you buy/change hosting.

thanks.

I had also similar experience of receiving duplicate email copy with exact same date/time/ip stamp. But It happened few months back and received two email copies sometimes. I have also the same thinking as by autoklimatechnik of user clicking more than once submit button.

@autoklimatechnik, can you let me know from which browser the user sent mail and you are getting duplicate emails?

thanks.

Yes it can fixed through editing the wp-config file manually. But I personally don’t recommend such advanced task unless you are an experienced PHP developer specially in wordpress environment.

Yep thats true. You shouldn’t allow caching for login user.

There are several factors you need to consider when like to optimize a site for page loading. You are using several of google fonts which have impact in page loading speed. Additionally, you have dumped large blocks of styles and scripts embedded directly which also impact for slow page loading. Your external styles and scripts files are not gizip enable. Finally it also depend on the selection of your hosting server.

@jcottone thanks for the tips! But there required a permanent fix in the upcoming release regarding this particular thing.

btw, if suppose a stable site with good ranks in google suddenly change all the links in the sitemap to https then how google will treat these redundant links. Will such situation lead to any penalty or loss of page rank?

If this can lead to loss of page rank, then its a matter of high concern and the author is advised to resolved this bug asap in the next release.

Can anyone share any experiences regarding the above mentioned situation…

Thanks!