MBWD

I ended up solving this a totally different way, by using the Advanced Custom Fields plugin to create a back-end interface for users to enter data that would then appear as a custom post type. Clients do have to know what they’re doing a little bit, but it’s not hard to show them and the fields themselves are pretty intuitive to fill out. I never did receive any response from the author of this plugin.

I am still having the same problem. I was able to use the development version to archive and re-install a test site on my localhost with no problem, so I’m wondering if this is a site-specific issue. When I run the scan in step 2 on this particular site, I’m getting errors like this:

Warning: Invalid argument supplied for foreach() in /nfs/c04/h06/mnt/180271/domains/mydomainhere.com/html/wp- content/plugins/duplicator/classes/utility.php on line 125
{“SRV”:{“OpenBase”:”Warn”,”CacheOn”:”Good”,”TimeOuts”:”Good”},”DB”:{“Status”:{“Success”:true,”Size”:”Good”,”Rows”:”Good”},”Size”:”1.87MB”,”Rows”:”1,415″,”TableCount”:16,”TableList”:{“wp_commentmeta”:{“Rows”:”54″,”Size”:”289.71KB”},”wp_comments”:{“Rows”:”19″,”Size”:”96.24KB”},”wp_duplicator_packages”:{“Rows”:”0″,”Size”:”3.88KB”},”wp_links”:{“Rows”:”0″,”Size”:”1KB”},”wp_options”:{“Rows”:”239″,”Size”:”485.73KB”},”wp_postmeta”:{“Rows”:”450″,”Size”:”155.49KB”},”wp_posts”:{“Rows”:”588″,”Size”:”838.27KB”},”wp_term_relationships”:{“Rows”:”10″,”Size”:”3.21KB”},”wp_term_taxonomy”:{“Rows”:”2″,”Size”:”4.08KB”},”wp_terms”:{“Rows”:”2″,”Size”:”11.06KB”},”wp_usermeta”:{“Rows”:”42″,”Size”:”13.6KB”},”wp_users”:{“Rows”:”2″,”Size”:”4.31KB”},”wp_wpb2d_excluded_files”:{“Rows”:”0″,”Size”:”2KB”},”wp_wpb2d_options”:{“Rows”:”7″,”Size”:”2.2KB”},”wp_wpb2d_processed_dbtables”:{“Rows”:”0″,”Size”:”2KB”},”wp_wpb2d_processed_files”:{“Rows”:”0″,”Size”:”2KB”}}},”ARC”:{“Size”:”127.59MB”,”DirCount”:”410″,”FileCount”:”3,875″,”LinkCount”:”0″,”InvalidFiles”:[],”BigFiles”:[“\/nfs\/c04\/h06\/mnt\/180271\/domains\/mydomainhere.com\/html\/wp-content\/infinitewp\/backups\/mydomainhere.com_manual_full_hashedzipnamehere.zip [63.85MB]”],”Status”:{“Size”:”Good”,”Names”:”Good”,”Big”:”Warn”}}}

I know that this refers in part to the wpb2d and infiniteWP plugins, but what’s the rest of it about?

This was also my first serious issue with them, but it’s bad enough that it, compounded with horror stories I’ve heard from other web developers, has convinced me it’s time to move on. To be clear, the tech support I’ve received from the Filipino staff has always been great. I like talking to them. It’s the North American end of things that seems to be seriously lacking in customer service skills. No one has even tried to explain what has happened or apologized for it.

When I called 1 and 1 the next day, they ended up telling me that it WAS their fault, but a week later they have still not offered me any explanation, except to say that it was done by their Abuse department because of some vague reason they never fully explained. I have actually LEFT 1and1.com since then and taken my business elsewhere, and I would strongly encourage anyone who asked me to do the same. This is hands down the worst customer service I have ever encountered. I’ve heard many others say the same. You can’t shut down a dozen websites arbitrarily and offer no explanation. You just can’t. It’s so incredibly unprofessional I don’t even know where to start.

I have to apologize. This ended up having nothing to do with your plugin. The problem was that I was trying to develop in a child theme while using MAMP. Lesson learned. Sorry to bug you.

The problem seems to have “fixed” itself over night. This tells me that 1and1.com is probably at fault, because I did nothing (was asleep, in fact). It makes me mad, because I called them TWICE to ask if it was on their end and they treated me as if I was stupid for asking. I will mark this as resolved. Thank you for your assistance.

Here in this article on twenty fourteen the author bemoans the fact that custom post templates are not available, not just in twentyfourteen but apparently in all default themes (scroll down to the bottom):

https://premium.wpmudev.org/blog/wordpress-twentyfourteen-theme-a-flawed-beauty/

I should add Legacy Homes is a custom page template I made using the Custom Template Page UI plugin.

I’m not terribly advanced at WordPress, but since no one has answered you in two days I will take a stab at it. I can’t really tell what’s going on just from reading the above or from looking at your example page. But I can say that if I was going to try this myself, I would go about it a different way. I would not try to make a whole new page template. That is something I would do in a different situation.

This looks to me like you are just trying to re-style a blog page, correct? So, yes, I would do this through CSS instead of making a new template which you may or may not have registered correctly. That is not a totally specific answer, but maybe it will help you think about the problem in a different way. Sorry I don’t have more help for you than that.

I will post a separate request.

Googling things like “how to use jquery in WordPress” seems to yield the universal result that the proper way to use jquery is to enqueue it in functions.php. Maybe this is only actually true for those who are developing themes or plugins. I am not trying to do that… I’m just trying to use jquery functions in the default theme. If this is not the case, then how does one use a function like #accordion in twenty twelve, for example?

I should add that the only way I am able to fix this error is by FTPing a whole new version of functions.php into my directory, overwriting the old version. This seems like a bit of a drastic move for a relatively minor error but it’s the only thing I’ve found that works. So my question is really not how to fix it, but why it happens in the first place.

Aaaaand this is why we clear our cache, boys and girls.

Thank you!

https://sample1.mahonebaywebdesign.com/

There’s nothing on it at the moment, obviously. The navbar and footer are currently the color I want them, that is, #FFFFFF. The default color for both these elements is #e8e5ce. But as I said, I could not get them to change by using the child theme. Instead I had to accomplish this in the stylesheet of the main theme.