Lewis Elborn

@caseproof, you were spot on! I discovered last week that another plugin was actively redirecting all users without the administrator role. I had to make edits to that plugin’s files to get it to work properly. That or disable the plugin entirely.

Thanks again.

Solved; Weirdly enough to need to save the fields empty and reload before you can enter new data and save.

Regards,
-B

@janjime I’m just a friendly face bud. Not a member of CF7 support. Just offering guidance where I can. ??

Glad all works now though.

regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.

Hey @newblogger75,

It would appear the element is being pushed. Add float: left; to your div.wpcf7-validation-errors class. Like this;

div.wpcf7-validation-errors {
    border: 2px solid #f7e700;
    float: left;
}

Float will lift the element from the document structure and should do the trick. Be sure to clear any elements below.

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.
• This reply was modified 7 years, 7 months ago by Lewis Elborn.
• This reply was modified 7 years, 7 months ago by Lewis Elborn.

I can confirm Flamingo working fine in correspondance with CF7 in Moz & Chrome.

Regards,
-B

Hey @jackgames,

Sadly if you didn’t install a CF7 DB when you built your form, to my knowledge there is no way to recover such information as it specifically states in the CF7 landing page.

I would suggest, installing the flamingo plugin, which is also developed by the CF7 Developer. It’s specific task is to help defend against situations like this one by saving all submitted queries into your database. (FLAMINGO)

Regards,
-B

@pimmesz, without a live link or some css & html examples of your code structure, we can’t really be of much use.

However, I can suggest the following;
If your using <li> tags as I think you are, ensure your list structure is not nesting like the following;

<ul id="myList">
  <li class="level-one">Lorum ipsum es timet.</li>
  <ol>
    <li>Var est vimus callus.</li>
    <li>Var est vimus callus.</li>
  </ol>
  <li class="level-one">Lorum ipsum es timet.</li>
  <li class="level-one">Lorum ipsum es timet.</li>
  <li class="level-one">Lorum ipsum es timet.</li>
  <li class="level-one">Lorum ipsum es timet.</li>
</ul>

Try adding, display:block; to your <li> elements.

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.

@bexvlad, We can’t do much with the little information your question provides. Do you have a live link to the issue? Or some examples of your css and html code structure?

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.

@cquinndesign + 1 for proper document structure! ??

@terocha From what I can understand from what your saying is that your form fails to send entirely when the user clicks submit. This could be a number of things and without seeing a live link to the problem I won’t be of much help sadly but I can suggest a few troubleshooting tips.

Firslty, if your using a recaptcha remove it and check to see if the form sends. (Sometimes recapatcha can be a bit troublesome.)

Secondly, open up the console, in your browser and send your form, does your form post at all?

@terocha,

IMO headers are always necassary unless instructed otherwise. Sadly, you cannot send HTML Markup through the form from the front end to my knowledge as it would be a huge security risk. The Option to enable HTML is for responses from the server to the user, I.e Auto responders etc.

You may be able to find a way around this online, but it would seem more hassle than it’s worth and I wouln’t reccomend it.

If you want to style your email so that when you receive it its well presented, you can insert the HTML within the Mail tab in CF7, then add your shortcodes where needed, this way when the user populates data it will find it’s way into the HTML template you have laid out then get sent.

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.
• This reply was modified 7 years, 7 months ago by Lewis Elborn.

@toscaburen Good question,

I’m not sure I know either, my only guess is that bounced Mail is lost in the either, or stored in logs somewhere serverside. Where though, I couldn’t say; but if someone else knows this I would also be keen to know.

Regards,
-B

Hey Jposcharnig,

Sadly if you didn’t install a CF7 DB when you built your form, to my knowledge there is no way to recover such files as it specifically states in the CF7 landing page.

I would suggest, installing the flamingo plugin, which is also developed by the CF7 Developer. It’s specific task is to help defend against situations like this one by saving all submitted queries into your database. (FLAMINGO)

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.

Hey Terocha,

Firstly a couple of questions, are you sending this through the form on your website, or sending it through the backend in the mail configuration tab?

Additionally, your code only fails to use the proper document stucture, html, head, body. Even email clients utiize these headers when building html emails.

Regards,
-B

• This reply was modified 7 years, 7 months ago by Lewis Elborn.
• This reply was modified 7 years, 7 months ago by Lewis Elborn. Reason: Additional Info

Intersting point,aurovrata. However, as she has mentioned that the form was working fine previously, it would be more prominent to ask if you have installed any new plugins or made any updates recently. Sometimes plugins can interfere with each other.

If you have installed some plugins or updated them, simply deactivate them one at a time and test your form again, if it works as before you know which plugin has caused the problem.

Regards,
-B

Hey Jan,

After checking your live version out, It would appear your submit button wasn’t dissapearing, just falling underneath the recaptcha. Add this to your Css file; you’ll see what I mean.

#submit {
	position: relative;
	margin-top: 7.5%;
}

This should do the trick.

• This reply was modified 7 years, 7 months ago by Lewis Elborn. Reason: Additional Info