Erin Bell

Have you tried editing the CSS file for your child theme[1]?

Below the @import rule, you can add additional styles. So it might be something like #container{width:500px} where #container is the id of the container you want to make smaller. Firebug[2] or other Developer tools[3] can help with identifying the container name.

[1] https://codex.www.ads-software.com/Child_Themes
[2] https://getfirebug.com/
[3] https://developers.google.com/chrome-developer-tools/

Put the media query at the end of your styles. Right now, you have it at the top, which causes those conditional styles (based on viewport size) to be overridden by what follows, which is global in scope (because it’s not limited by the media query). Make sense?

I would recommend against this approach. It’s bad for sharing, creates a lot of work and introduces unnecessary friction and maintenance complexity. If you’re already using a responsive theme, why not stick with that and create a child theme that uses a lightweight device detection script (like the ones below) to determine if the visitor is on a mobile device? That way you have a baseline functionality that works for everyone and can add/remove/enhance as needed based on device detection.

See for example:
https://mobiledetect.net/
https://detectmobilebrowsers.mobi/
https://code.google.com/p/php-mobile-detect/

What exactly do you want to change for mobile/desktop users?

Upgrade to latest version did the trick.

Just resent from another email account and received a response ticket. Thanks.

Hi @soflyy, I’ve submitted a couple tickets via the email listed at https://www.wpallimport.com/support/ and have received no reply. Perhaps my message got filtered or otherwise lost? Please confirm here if you have not seen my messages. I will resend from another address or something if need be. Thanks — E

Can you post the code block from your theme that begins with something like …

if have_posts() : while have_posts() : the_post()

Looks like your links on each of those sites all end with ‘/postname’ which makes me think that should actually be a variable or something (i.e. $postname).

Did you happen to upgrade to WordPress 3.3 around the time this started? Could be that something in your theme is no longer compatible with the latest WP release.

Looks like you need to double check that you’ve set up your domain forwarding as a Permanent Redirect.

Are you by chance forwarding the page from one domain to the other in your theme header? Possibly after the first domain loads. It looks that way and would explain the double indexing, but it’s hard to tell for sure.

Try removing any inline forwarding and just forwarding from your DNS record (e.g. in your GoDaddy or other host control panel), again, making sure to set as Permanent Redirect.

Hope that helps – E

Hi,

Sounds like a job for custom post types, which allows you to create a custom post entry template. That way you can present users with a structured form that only contains the fields relevant to a business directory (like address, contact info, hours of operation, etc).

Check out Custom Post Type UI:
https://www.ads-software.com/extend/plugins/custom-post-type-ui/

This will give you a very easy interface for generating the code you need. It creates both custom post types and custom taxonomies (that work like tags/categories).

Or you can do so directly by consulting the Codex entries at:
https://codex.www.ads-software.com/Function_Reference/register_post_type
https://codex.www.ads-software.com/Function_Reference/register_taxonomy

There are some good resources listed on that page, a Google-ing will also yield some very good tutorials.

-Erin

I don’t know anything about Squeeze pages, but you could probably create a page template [1] using your old theme (we’ll call it theme-2) as a basis.

So take the page template you want to use from theme-2 and move it into your current theme directory. Do the same thing with the style.css, header.php and footer.php files from theme-2. IMPORTANT: rename them to something like page-theme2.php, header-theme2.php, footer-theme2.php and style-theme2.css. In the page template, edit get_header() [2] and get_footer() [3] so they look something like:

<?php get_header('header-theme2') ;?>
<!-- your page content goes here -->
<?php get_footer('footer-theme2') ;?>

You will also want to edit header-theme2.php so it calls the right stylesheet:

<link rel="stylesheet" href="PATH/TO/STYLESHEET/style-theme2.css" type="text/css" media="screen" />

Also note that it’s very possible your old theme has a bunch of custom functions that will not work without also moving those over (as needed) from theme2/functions.php.

This is actually going to be a fair amount of work and may be a bit involved, depending on your comfort level with WordPress themes. It might be easier to just find whatever the Squeeze functions are on your old page template and copy them over to the new theme.

[1] https://codex.www.ads-software.com/Pages
[2] https://codex.www.ads-software.com/Function_Reference/get_header
[3] https://codex.www.ads-software.com/Function_Reference/get_footer

Thanks so much for doing this. I just migrated an old site onto a new server (without considering that PHP 5.3 might be an issue for old/deprectated plugins). This is perfect and the switch to the new plugin is seamless, as all the database tables and functions seem to have remained in place. I only had to manually adjust a bit of CSS (so maybe some of the HTML changed but very little, thankfully). Again, many thanks. A real lifesaver.

Um, it appears I was running that regular expression on the wrong variable. How about this one, which adds an extra step to the WP sanitize_user() process (which leaves those pesky dots in place):

$uarray = split( '@', $user['email'] );
$user['username'] = sanitize_user( $uarray[0] );
$user['username'] = preg_replace('/[^a-zA-Z0-9]/', '', $user['username']);

Okay, actually this may cause errors in some instances [related post]. Not sure why, but it works most of the time.

Catchable fatal error: Object of class WP_Error could not be converted to string in... path/to/formatting.php on line 2829

Got this error also, upon importing a number of users (I don’t have any other details, unfortunately, as it was reported to me by another user). It seems that the users were imported successfully despite the error.

Catchable fatal error: Object of class WP_Error could not be converted to string in… path/to/formatting.php on line 2829

Worth noting that I just enabled a caching plugin. I will try to replicate with and without that plugin, since that was my only recent change to the site.

I also have a minor hack in place that I doubt has anything to do with this: https://www.ads-software.com/support/topic/strip-non-alphanumeric-characters-from-generated-usernames?replies=1

Also have the same problem. Also have no answer.