Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter steve13565

    (@steve13565)

    I did a little investigation of the post_metadata issue. The bug is clearly with Ninja Forms.
    Here is all the info they need handed to them on a platinum platter for free. Will they use it? I have done all the hard work.

    So the coclusion is that Ninja Forms inserts post metadata like:

    (1463, 541, ‘_field_27’, ‘Steven’),
    (1464, 541, ‘_field_28’, ‘Greenberg’),
    (1465, 541, ‘_field_29’, ‘steve@s__________.___’),
    (1466, 541, ‘_field_26’, ‘other-suggest-topic-in-the-first-line-of-your-explanation’),
    (1467, 541, ‘_field_25’, ‘Topic: test\nSee if removing reCaptcha helps on export.’),

    Whereas Customizr Pro inserts fields like

    (1461, 541, ‘tc-thumb-fld’, ‘a:2:{s:9:”_thumb_id”;b:0;s:11:”_thumb_type”;s:10:”attachment”;}’),

    There should be no confusion. Why is Ninja Forms exporting meta data with the meta_key of tc-thumb-fld?

    • This reply was modified 7 years, 10 months ago by steve13565.
    • This reply was modified 7 years, 10 months ago by steve13565.

    What’s the problem? Google reCaptcha worked for me with this plugin. Later I read a description of why I don’t need Google reCaptcha, so I have turned it off.

    Did you put the suggested Google reCaptcha code on the page or post where you used the form?

    • This reply was modified 7 years, 10 months ago by steve13565.
    Thread Starter steve13565

    (@steve13565)

    As I said in a private message, I didn’t realize that the authentication required a pop-up window. I have pop-ups disabled in my browser. I didn’t notice any warning about a failed pop-up if my browser gave me a warning. Since I connected my WordPress site to Google Analytics the “hard” way, I haven’t bothered to go back to look at the plugin.

    OK, here is the source code that Google chrome sees on my home page. I have replaced the less than sign with angled quotes to show you what it almost looks like. The UTF-8 is embedded in the code. I don’t think the logic involving interrnet explorer prevent s Google Chrom from seeing the UTF-8 declaration. Correct me if I am wrong.

    «!DOCTYPE html>
    «!--[if IE 7]>
    «html class="ie ie7" lang="en-US">
    «![endif]-->
    «!--[if IE 8]>
    «html class="ie ie8" lang="en-US">
    «![endif]-->
    «!--[if !(IE 7) | !(IE 8)  ]>«!-->
    «html lang="en-US">
    «!--«![endif]-->
    					«head>
    				    «meta charset="UTF-8" />
    				    «meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" />
                				    «meta name="viewport" content="width=device-width, initial-scale=1.0" />
    				    «link rel="profile"  />
    				    «link rel="pingback"  />
    
    				   «!-- html5shiv for IE8 and less  -->
    				    «!--[if lt IE 9]>
    				      «script src="https://justicefa.org/wp-content/themes/customizr-pro/inc/assets/js/html5.js">«/script>
    				    «![endif]-->
    				            «style id="dyn-style-fonts" type="text/css">
                /* Setting : body */
    
    • This reply was modified 7 years, 11 months ago by steve13565.

    Let me see if this makes it past the editor.

    «meta charset=”UTF-8″ />

    This does not seem to be going through. Let me see if the following line makes it past this editor:

    meta charset=”UTF-8″ />

    The following is the top of the source ccode that Google Chrome sees. UTF-8 is mentioned embedded in some logic. It seems to me that Chrome ought to see it, but maybe ytou can tell if I am right about that or not.

    <!DOCTYPE html>
    <!–[if IE 7]>
    <html class=”ie ie7″ lang=”en-US”>
    <![endif]–>
    <!–[if IE 8]>
    <html class=”ie ie8″ lang=”en-US”>
    <![endif]–>
    <!–[if !(IE 7) | !(IE 8) ]><!–>
    <html lang=”en-US”>
    <!–<![endif]–>
    <head>
    <meta charset=”UTF-8″ />
    <meta http-equiv=”X-UA-Compatible” content=”IE=9; IE=8; IE=7; IE=EDGE” />
    <meta name=”viewport” content=”width=device-width, initial-scale=1.0″ />
    <link rel=”profile” href=”https://gmpg.org/xfn/11″ />
    <link rel=”pingback” href=”https://justicefa.org/xmlrpc.php” />
    
    <!– html5shiv for IE8 and less –>
    <!–[if lt IE 9]>
    <script src=”https://justicefa.org/wp-content/themes/customizr-pro/inc/assets/js/html5.js”></script>
    <![endif]–>
    <style id=”dyn-style-fonts” type=”text/css”>
    /* Setting : body */

    [Moderator note: code fixed. Please wrap code in the backtick character or use the code button.]

    • This reply was modified 7 years, 11 months ago by bdbrown.
    • This reply was modified 7 years, 11 months ago by bdbrown.

    Oh, I have pop-ups disabled. Maybe there was a warning that I just did not notice.

    I have tried everything I can thing of to get 2.0.3 to authenticate with Google. Nothing positive happens when I press the authenticate button. What does an access key from google look like. Is it the UA-12345678-1, or is it the 12345678? I’ve tried them all, and nothing works. I am deactivating the plugin and going back to doing it the “hard” way.

    Well, here is the issue. The source code that is generated in Firefox, Internet Explorer, Safari, and Opera is:

    I have to screw up the encoding of the less than sign because this crazy editor insists on interpreting the code into the symbol.

    & lt;img src=”https://justicefa.org/wp-content/uploads/2016/12/Diversity-2.jpg&#8221; alt=”” />

    However, in chrome it generates

    & lt;img style=”height: 400px;” src=”data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7″ data-src=”https://justicefa.org/wp-content/uploads/2016/12/Diversity-2.jpg&#8221; alt=”” />

    I got the chrome code in the other browsers when I had the WordPress classes as generated by inserting from the media library, but when I took out the classes, then I got the src to point to the jpg image. By the way, the code that fails in Chrome works in the other browsers.

    I am using Windows 7 for all of this work.

    GoDaddy threw in a whole bunch of unwanted plugins when I let it set up my WordPress for me. Also I am using Customizr-pro theme. I wish I hadn’t taken the shortcut and had done my own WordPress install like I have done in the past.

    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.
    • This reply was modified 7 years, 11 months ago by steve13565.

    Yes, the link you pointed to said there was a bad copy of the update on one of the servers, and that it has been fixed. I just did a successful update. Thanks.

    It would be interesting to see someone try the manual installation method that d4z_c0nt suggests. Although, if the style.css file is missing with other install methods, it would be hard to imagine that is is in the zip file.

    Well, I did look in the zip file at the above link, and style.css is there as well as inc/init.php which was missing from my installation.

    The install zip file is obviously quite broken. I also had a child theme that broke, but I eventually tracked it down to the bad parent theme installation.

    I got exactly the same messages you did, when I tried reinstalling the theme after a failed update of the theme.

    Luckily I have nightly backups of my site. I just reinstalled last night’s version of the theme, and all is well.

    I just noticed that SU released a new version. It had something to do with an interaction between Font-Awesome and https:.

    I have no idea if this fix addresses thermador’s issue.

    beet09,

    When you are viewing a web page that displays the font awesome icons, can get your browser to show you the HTML source code? Then use your browser’s text search to look for “font-awesome” to see if the link is actually there before you put in the link manually, but perhaps the original is not quite right.

    Maybe there is a clue there as to what is going wrong.

Viewing 15 replies - 1 through 15 (of 20 total)