Forum Replies Created

Viewing 15 replies - 16 through 30 (of 62 total)
  • Thread Starter edtiley

    (@edtiley)

    Cirtis,

    PS — I just looked back at the form that creates the record in another method of the class, and that’s where the error started thanks to cut and paste.

    Somehow though jQuery and AJAX covered that sin (type = ‘post’) because it picked up the proper values, then POSTed them when calling the callback function.

    Sheesh!

    Thanks again!

    Ed

    Thread Starter edtiley

    (@edtiley)

    Curtis,

    > You could add method=”post”

    Dayum!!!

    I just looked at that code above and saw it!

    <form type='post'> // Yeah, that works NOT!

    Sheesh, do I feel stupid. Perhaps I should change type to method huh?

    Thank you, sir. Sometimes it just takes another pair of eyes to open your own.

    Ed

    (Also a DC area transplant living in Florida)

    Thread Starter edtiley

    (@edtiley)

    Ron,

    Strange of strange! It started working on its own. Checked it this afternoon and the issue had cleared.

    I don’t have much of an insight, but the only thing I can think of is that I deleted the parking entry for the domain a couple of times and redid it, which may have given the DNS an upset stomach. Both domains were set to the proper NS server long before I started working on this, so is shouldn’t have been a DNS issue. I waited overnight in case it was a propigation issue before I wrote the original message.

    All I know is that it is working, so it is onward and upard to the next thing, which is being able to create and map subdomains of virtual subsomains of the primary domain for the network. I think I read somewhere (Mika?) that there is a plugin that lets you create sites as subdomains of a mapped name. (i.e. ForgottenCoastFishing.com is mapped onto fish.ForgottenCoastNetwork.com, and you want to create billsbait.ForgottenCoastFishing.com)

    That’s another thread, however, if I can’t get it working.

    Thanks for your help and your plugin,

    Ed

    Thread Starter edtiley

    (@edtiley)

    Ron,

    I’ve contacted, I’ve been assured by tech support, I’ve tested and mod_rewrite is working.

    I don’t know why I didn’t think of it before but the fact that
    http://forgottencoastfishing.com/wp-admin/ takes me to the dashboard of fishing.forgottencoastnetwork.com and shows as forgottencoastfishing.com in the address bar proves that mod_rewrite is enabled and working don’t you think?

    I can change the permalink configuration and it ALL works. I can set and use the default:
    http://forgottencoastfishing.com/?p=1
    or
    set permalinks to
    /%year%/%monthnum%/%author%/%postname%/
    http://forgottencoastfishing.com/2015/01/fcnadmin/hello-world/

    The only thing that doesn’t work is the bare naked
    http://forgottencoastfishing.com
    brings up the front page of the network’s home domain and shows
    as http://forgottencoastnetwork.com in the address bar.

    I’ve trashed the whole setup and rebuilt it from scratch twice today, and I’m still getting the same result.

    Thoughts?

    TIA,

    Ed

    Thread Starter edtiley

    (@edtiley)

    Ron,

    Sorry, been on the road all day so I haven’t acted on it yet, but….

    mod_rewrite isn’t normally a problem with Hostgator which is why I didn’t even think about it as a source of the problem. When rewrite is turned on in .htaccess, WP’s permalinks work “pretty” as you please.

    I think I’ve managed to bung up the database or something. I’ll be spending my whole work day on it tomorrow, and will report the result.

    I’m optimistic.

    Thread Starter edtiley

    (@edtiley)

    According to the HostGator docs mod_rewrite.c is a part of all their server configs, so it should be turned on by the call to RewriteEngine On.

    Here’s the content of .htaccess:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /

    RewriteRule ^index\.php$ – [L]

    # add a trailing slash to /wp-admin
    RewriteRule ^wp-admin$ wp-admin/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
    RewriteRule ^(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]
    </IfModule>

    # END WordPress

    Yet phpinfo() doesn’t show it as turned on.

    Wonder where I went off the tracks…

    Thanks,

    Ed

    Thread Starter edtiley

    (@edtiley)

    Apparently I’ve put this in the wrong forum.

    I’m marking this as resolved, since I can’t delete it, and reposting in Plugins and Hacks.

    Thread Starter edtiley

    (@edtiley)

    omacs,

    Did you ever get a reply or a workaround?

    Thread Starter edtiley

    (@edtiley)

    omacs,

    I too think it would be great. It’s the only real issue I have with the plugin. I’d love to have all my commenting on FB, but there are simply some pages that shouldn’t allow comments.

    I just launched a new brand new site ( http://www.apalachicolabay.com ) and would like to get this worked out before I start getting comments. I’ve had to turn the FB comments off beacuse it’s affecting design issues.

    I’m afraid I’m going to loose the very first comments after the switch back to FB comments. It’s either that or write a comments plugin that embeds the code from the FB developers’ Social Plugin generator into the end of the_comment() at the end of pages and posts where comments are allowed.

    Thread Starter edtiley

    (@edtiley)

    WordPress has two basic concepts: display comments if the post contains comments; display a form soliciting new comments if the post allows new comments.

    OK, so why if a page has no comments, and the page doesn’t allow comments, why am I getting comments forms?

    Thread Starter edtiley

    (@edtiley)

    But, but, but… I never said anything about read-only.

    I’m talking about a brand new site that has no existing comments.

    I create a page, I uncheck Allow Comments, then publish it. I view the page, and no comment activity shows on the page. I enable FaceBook commenting by checking posts and pages.

    Now the page has Facebook comments enabled. Allow comments is still unchecked but the plugin is overriding that setting.

    That can’t be right can it?

    Thread Starter edtiley

    (@edtiley)

    Niall,

    Just reread what I wrote last night, and my apologies if the tone seemed a bit strident. I was dead tired at the end of the day.

    Since writing that note, I’ve discovered that the behavior I described is only on the front page. On subsequent pages the comments area is coming from the FaceBook plugin, and is accepting comments regardless of the contents of the Allow Comments checkbox in the WP Admin’s editor.

    The behavior I described last message is only happening on the front page, and may be the result of how it is built (with custom CSS and HTML). I’m going to try to figure that one out next.

    Still this isn’t a theme thing, as Twenty Thirteen has the same behavior – e.g. allowing comments when comments are disabled for a page or post.

    Thanks,

    Ed

    Thread Starter edtiley

    (@edtiley)

    Thanks paulwpxp,

    Sample urls no longer valid.

    Thread Starter edtiley

    (@edtiley)

    Excuse me, sir, but I said nothing of a theme.

    The checkbox to allow or disallow comments and its companion trackbacks has nothing to do with any theme. Both are native to WordPress.

    Those pages where the checkboxes have been cleared (not ON) show the “unenhanced” comment form which allows a comment to be entered, which is assumedly then rejected by WP because the checkbox enabling comments is not checked.

    Previous to the installation of your plugin, the WP settings were being handled appropriately by the theme. BTW, that theme is Weaver II Pro.

    However, the behavior I cite is reproducable in Twenty-Thirteen as well.

    I have marked this topic as “not resolved.”

    Thanks,

    Ed

    Thread Starter edtiley

    (@edtiley)

    >>> contributors ‘own’ a site where they can only write, it’s gonna be a PITA.

    No, ma’am, I suppose a contributor would equate to administrator in the normal WP nomenclature.

    They would be able to upgrade to have premium features. Whatever the technical arraingements, those are the folks I called Premium Contributors.

    In your WordPress Multisite 110 ebook (I definately owe you a contribution for that one! Mucho worth_it!) you have a chapter about restrictive sites, do’s and don’t’s. I plan to be restrictive even a little above and beyond some of the techniques metioned there.

    Perhaps I’m being overcautious and paranoid, but if you’re going to have a baby you should childproof your home. If you’re going to attempt a political blog based on enforcing the basic rules of civil discourse, you should learn to herd cats.

Viewing 15 replies - 16 through 30 (of 62 total)