danielpataki

Hi there @sattarmalik1,

WordPress updates can be initiated from Dashboard->updates. You can update your core and themes/plugins from there.

Updates do not affect your content so there is no need to worry. I’ve been working with WordPress for 8 years and have never experienced an issue where content was affected. That said, if you feel a bit afraid to do it you can always create backups.

The Codex has a great article on Backups. I also recommend VaultPress as a backup solution. It is cheap, super easy to use and made by the Atomattic (who make WordPress).

Hope this helps!

Daniel

Ah, there is some more info here. This is not a 404 error, the error is caused by a DNS lookup issue, here’s the fill message Chrome spits out:

The server at test.feelingpurpose.com can’t be found, because the DNS lookup failed. DNS is the network service that translates a website’s name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.

I have my money on the subdomain not being set up. In some cases I have seen a 10-30 minutes lag between setting up subdomains and them actually working. I’m not sure what the reason for this is, but it has happened.

While this still could be a WordPress issue it seems less likely, I would definitely wait to see what your host has to say. While you wait I would recommend taking a look at using FTP ?? It would allow you to see if the WordPress files are in the correct folder and so on.

Daniel

Is it possible to share the link? I doubt it will yield anything useful but its worth a shot. This sounds like the installer didn’t do its job properly but it’s difficult to say. If you installed it on a subdomain are you sure the subdomain has been created?

If you have FTP access to your website or you can upload files through a control panel I would recommend installing WordPress yourself. There is a long article on it in the Codex.

Daniel

Hi @boygirlboygirl,

The causes of this could be pretty varied. Can you try it again but deactivate all plugins and enable a default theme like Twenty Fourteen?

That would help rule out any third party issues.

Daniel

Hi there @tess.copeland,

Does this happen after login, or does the error show up after you log in? You can go to https://yoursite.com/wp-login.php directly to figure this out. Also, does the front page of your website load properly?

Normally you don’t need to do anything special to access the admin so this is either an installation error or in rare cases perhaps it could be a file permission error which you could talk to your host about.

Daniel

Hi there thecatz,

This would be extremely difficult. The native WordPress search uses the WP_Query object which is set up to use the posts table. The only way around this as far as I can think right now is if you write a custom search UI and query yourself.

I would suggest using a custom post type instead. Custom post types are highly configurable (you can choose to display/hide them in the front/backend, add specific features and so on) and can be included in searches and other queries.

I suggest taking a look at the Custom Post Types article and the documentation on register_post_type() to get started.

I think this is a pretty big flaw in WooCommerce now that I come to think of it, it should at least be changeable via a setting. Do let us know if you find out anything!

Daniel

No worries ?? That’s correct, but I do want to add in functionality to make it even better. This is something I’ll chalk up as a feature request. It might be something we will only add to the pro version. If this is the case we will of course send it to you for free ??

Daniel

Hi @justuscook,

I’ve worked with WooCommerce before but this is not something I needed to solve so I won’t be much use here. A casual search brought up surprisingly few results, here is one, but it’s not an ideal solution:

https://stackoverflow.com/questions/24379214/prevent-automatic-login-when-register-in-woocommerce-and-redirect-to-login-page

With code this can obviously be done, but as it stands it looks like this can’t be disabled easily. If I find any evidence of the contrary I’ll let you know!

Daniel

Hi there @justuscook,

The email verification works like this: Go to Settings->General and make sure to check the checkbox next to “Anyone can register”. Then, log out and go to https://yourdomain.com/wp-login.php.

You should see a register link. Enter your username and email. WordPress will send a password to that email address with the username, password and login link.

There is a plugin named User Activation Email which adds a bit of extra security, perhaps this will do.

Hope I could help!

Daniel

Hello there ??

I’m not sure it would work this way, here’s why: The gallery is for displaying images that belong to more than one category. The title of each pile would be a specific category, so you would see three piles: “Portrait”, “Landscape”, “B&W”. When you click on any of these, the gallery folds out to show what is underneath. If this is what you need then yes, images are pulled dynamically, so if you upload a new “B&W” photo it will automatically show up.

You will be able to use any plugin which is capable of adding taxonomies. I haven’t tested the ones you mentioned but they should be fine ??

Daniel

Thanks Oscar,

If you need anything else or have any feature ideas let me know here, or straight on Github ??
https://github.com/danielpataki/acf-google_font_selector

Daniel

Thanks Oscar,

The plugin should now load a cached version of all fonts from a file if your API connection fails, so it shouldn’t break no matter what ??

Daniel

Hi there,

Sorry for the long wait, I didn’t receive notifications. If this is still relevant and hasn’t been fixed can you give me a bit more information about the problem?

Thanks!

Daniel

Sorry about the lateness, I wasn’t getting notifications! I think this has now been resolved, if this is still an issue let me know!

Daniel