[Steven Zahm]

@ Steven

re: Are there styling options I’m missing somewhere?

Sorry, but there are no styling options. Form is designed to be plug in and play.

[Steven Zahm]

@ Alfonso

The root of the issue is permalink support as you have figured out. The web host is running some really dated software (I do not think they are even supported anymore and may be a security risk to your site):

Server:Microsoft-IIS/6.0
X-Powered-By:ASP.NET
X-Powered-By:PHP/5.2.5

I know IIS/6.0 needs tweaks in order to properly support mod_rewrite without the index.php being in the URL. This is something the web host will have to do. Here’s a Google search that results with others asking the how to remove index.php and answers..

This page may be the exact answer to solve the problem.

Hope this helps!

[Steven Zahm]

@ david1421

You need to add the enable_category_by_root_parent=true option to the shortcode. Here’s a link to the FAQ with a little more and an example.

Hope that helps!

[Steven Zahm]

@ Matt

You would add this to your template:

$region_1 = $entry->getMeta(
        array(
            'key'    => 'region_id_1', // This should match exactly the field id used when registering the custom field.
            'single' => TRUE        // Do not change this.
        )
    );

echo if ( $region_1 ) 'All of Minnesota.';

Hope that helps!

[Steven Zahm]

@ gail

There seems to be a conflict between CloudFlare, Swiftype and Autoptimize which is causing javascript errors on your site which is turn is breaking cMap, Form and perhaps other stuff which might not be as obvious.

Disabling Autoptimize on the directory page seems to making it work again even though the javascript errors still exist. My guess that has to do with the order in which the files are loaded by Autoptimize but Swiftype seems to be the source of the javascript errors. So I suggest trying to disable that first which should fix the javascript errors.

Hope that helps, let me know.

[Steven Zahm]

@ Jacki

Great to hear you figured it out.

[Steven Zahm]

@ Saffron Quantrell

I looked at the page and it seems to be working correctly. Let me know if you need any further help.

[Steven Zahm]

@ dominic loiacono

Those options actually originate from Link, not the Login widget, so you would use the connections_link text domain.

Hope that helps!

[Steven Zahm]

@ Monica Stuckey

A filter where?

[Steven Zahm]

@ David

Which version of Connections did you install? The latest, 8.5.14, removed direct use of the core WordPress function get_query_var() because of other plugins and theme occasionally breaking it resulting in the error you are seeing. The latest version implements a wrapper function which checks to make sure the function is not broken before it is used and if it is broken fails back to an alternative method so Connections can keep doing its thing even though that part of WordPress is broken.

If you’d like to read the gory technical details here:

http://connections-pro.com/support/topic/fatal-error-in-query-php-line-28/#post-372136

You situation seems to be a little different. I’ve never seen this happen in the admin the Architect plugin must being doing something interesting. I suspect Architect plugin just might, maybe, cause you other troubles with other plugins though it might be as obvious. I only mention it so you can keep it in the back of your mind incase you run into other odd little issues that can not be explained.

Now, all this said, If you were installing the latest version and still receiving this error, I’ll need a copy of Architect so I can see what it is doing. I might have to add another other checks to make sure get_query_var() is not broken before trying to use it.

[Author]

Posts