Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Thank you again for you help and quick replies! 🙂 I’ll see if it looks like I’m up to moving Site-2 without crashing the site. 😉 If so, I’ll let you know how it works out.

    Thank you. Please take a look at my detailed notes regarding the directory hierarchy for the 5 sites. I mentioned it in my support request because I wondered if settings made to AIOWPS in Site-2 might be affecting Site-3, Site-4, and Site-5 because of where the WP site installations are located in relation to each other in my hosting account.

    Site-2 is installed in /home/public_html. It is the site I used to open my hosting account. Sites 3, 4, and 5 are add-on domains. They are installed one level lower in the directory hierarchy at:

    I’ve never moved a WordPress installation before, but I’m wondering if the conflicts would be eliminated if Site-2 were moved down a level to a new directory, /home/public_html/, putting it at the same level in directory hierarchy as sites 3, 4, and 5. That would be instead of Site-2’s current location at /home/public_html, which is one step above the others in the directory hierarchy.

    An extra note that might help: Settings changes to AIOWPS made to Site-1 have not had any carry-over affect on sites, 2, 3, 4 or 5. Site-1 is an add-on domain located at a different level in the directory structure at /home/

    • This reply was modified 2 years, 10 months ago by DaveKinskey.

    IMPORTANT ADDENDUM: I forgot to mention one step in the fix.

    You need to add the following code to functions.php:
    add_theme_support( ‘title-tag’ );

    If the moderator wants to insert the info in my previous reply, that would be fine, or delete both of my replies, alert me to the fact, and I’ll post again with the missing step included. I apologize for the confusion.

    Neither of the solutions above worked for me, but your posts and others helped me discover another method that did work. Here’s a summary of what I did to resolve the duplicate titles caused by SEO Yoast in Cyberchimps themes iFeature Pro 5 and iRibbon Pro 2:


    Do NOT enable “Force rewrite titles” in the Yoast SEO plugin on the SEO -> Titles & Metas page. If you “Force rewrite titles”, it will slow down your site.

    – You need to use a CHILD THEME so you won’t lose your changes and improvements when your original theme is updated. Your child theme will require at least its own folder, a style.css file, and a functions.php file, and in this case, you also need a header.php file, which is one of the keys to getting rid of the duplicate titles.

    – In cPanel, copy the complete header.php file from the original theme to the child theme. Or download a copy from the original, and then upload it to your child theme via FTP.

    – In the child theme’s header.php file, delete the title element, which will be between <title> and </title>. such as <title><?php wp_title(”); ?></title> or
    <title><?php bloginfo(‘name’); ?><?php wp_title(); ?></title>

    When editing pages or posts:

    – DO fill in the Title in the default WordPress title field at the top of the edit page. If you do not fill in the title at the top of the edit page, it will be much harder to find individual pages in the Dashboard, since the pages won’t have titles.

    – Do NOT fill in the SEO Title in the snippet editor in the Yoast SEO section of the edit page. Leave it at the default %%title%%%%page%%%%sep%%%%sitename%% or else you will get duplicate titles. (It’s good to fill in the meta description in that section.)

    The steps above eliminated all duplicate titles on multiple sites which used those two themes. I hope this helps others who have the same problem.

    Hi. Thanks for prompt replies.

    Unless I’m misunderstanding you, what you’re requesting is exactly the testing I described in my support request as having already done. I tested repeatedly and identified “Prevent Hotlinking” as the cause of “Problem #2”. Enabling “Prevent Hotlinking” in Site-2 causes the image problems in Site-3, Site-4, and Site-5. As I noted, Site-3 and Site-5 don’t even have AIOWPS installed. Toggling “Prevent Hotlinking” off in Site-2 eliminates the problems in the other 3 sites.

    Also, toggling off “Whitelisting” in Site-2 cures “Problem #1”, which blocks the administrator of Site-3 from accessing her WP Dashboard. Whenever I turn on “Whitelisting” in Site-2, it causes the log-in problem to reappear in Site-3.

    Yes, all 5 sites have the same IP address.

    Thanks. I included my site name in the original posting, but not as a link. I wrote it out as locatehome-dot-com. Currently, Photon is not activated in Jetpack on my site because of the problem. Here is a clickable link:

    The space in the column, “Locked Status”, is blank (empty) for IP addresses in the ranges blocked.

    Well, I answered my own questions by accidentally deactivating Media Library Categories when I meant to leave it activated. When I reactivated the plugin, I still had my categories intact, and all categories were reassigned to images as they had been before deactivation. Great! You can mark this as resolved.

    Thanks so much for developing this plugin. 🙂

    SOLUTION: Until this plug-in is fixed, the configurable plug-in “External Links” works fine in WordPress 4.1, without deleting embedded audio. It also offers a variety of options.

    I am also running WordPress 4.1 with WordPress SEO by Yoast 1.7.1., and I have the same problem. I enter information on existing pages in a child theme of iFeature Pro 5 by Cyberchimps, but nothing will save in the Focus Keyword, SEO Title, and Meta Description fields. Oddly, it will save on one page, but nothing saves in WordPress SEO by Yoast on the other page.

    Even on the page where the fields were saved, Focus Keyword section fails to see keywords on the page sometimes, even if the page title is entered word for word, and under “Your focus keyword was found in:”, everything always says “No,” even when the words or phrases are on the page.

    Thanks again, Ryan! I’ll see how it goes with “Date-637” for now. If I still get some spam, I’ll try eliminating the number or making it just one digit, in case the spambots are programming to spot a “hyphen plus three digits” to avoid that field, since that’s the naming format Honeypot uses by default.

    Can there be a space between the name and the number? If not, I could also try changing the hyphen to an underscore in case the spambots are looking for that hyphen.

    Thank you so much, Ryan, for your answer to my question. 🙂 I’ll try changing the field. From what you said, it sounds like if the name is not “enticing” enough, the spambots may ignore the trap.

    I’ll try changing the name of the honeypot element on my contact page,

    The current source code shows text that says, “Please leave this field empty.” Can’t the spambots read that in the source code? Is that a problem? Below is the source code from the page of the current honeypot element, before changing the name, as you advised.

    <p><span class=”wpcf7-form-control-wrap Checkbox-97-wrap” style=”display:none !important;visibility:hidden !important;”><input id=”Checkbox” class=”wpcf7-form-control wpcf7-text” type=”text” name=”Checkbox-97″ value=”” size=”40″ tabindex=”-1″ /><small>Please leave this field empty.</small></span></p>

    By the way, is it necessary to leave the “-#” in the honeypot name? The new honeypot name is Date-637 and I named the id “Date”. The new code inserted is: [honeypot Date-637 id:Date]

    Can I get rid of the number? Does it matter or not?

    The new source code on reads:

    <p><span class=”wpcf7-form-control-wrap Date-637-wrap” style=”display:none !important;visibility:hidden !important;”><input id=”Date” class=”wpcf7-form-control wpcf7-text” type=”text” name=”Date-637″ value=”” size=”40″ tabindex=”-1″ /><small>Please leave this field empty.</small></span></p>

    Thanks so much. 🙂

    Thank you for the quick reply.

    All in One SEO seems to have a way to write title tags or overwrite the original title tags. Is there no function within All in One SEO that can handle writing unique title tags for a page that shows search results from an offsite database? Google does crawl and index the individual homes listed for sale in the MLS database, which is good for SEO, but the duplicate titles are a problem.

    If nothing can b, would the only solution be if the developer of the flexmls® IDX Plugin can add a function to create title tags for the pages brought up in the database search and somehow add it to the head of my page being used to frame the results? Or is that impossible?

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