bindlegirl (a11n)

As @braehler suggested, you can edit the template files. Check out the template overrides documentation here:

https://wpjobmanager.com/document/template-overrides/

Hi there!

There is no optimum number of jobs you can publish using the WP Job Manager plugin. The load and the speed will mostly depend on the configuration of your server. The more jobs you have the better (faster, more optimized) server you need.

Do you need to have all the 20 000 jobs in your database? If the answer is yes, then you need to look into tuning your server better to serve the needs of your site (and database) better.

@inempleo

Depending on how you built your templates, you can try filtering the posts by status. Active jobs have the status set to publish that is a standard WordPress status: https://www.ads-software.com/support/article/post-status/

Hi David,

Since you have removed the translation files from your server and the site is still loading the translation files, I would recommend you try clearing any site/server cache to see if that is the reason you still see the translations.

You may want to ask your host to help you figure this out.

Have you tried switching the theme to one of WordPress default ones like Twenty-twenty?

Hi there!

If you are using [jobs] shortcode to display jobs on the taxonomy page you can add the post_status="publish" parameter to display only active jobs.

For example, the shortcode will look like this:

[jobs post_status=”publish” categories=”administracion-de-empresas” show_filters=false]

You can check out the shortcode reference here: https://wpjobmanager.com/document/shortcode-reference/

• This reply was modified 4 years, 4 months ago by bindlegirl (a11n).

Hi there!

Any ideas why this one random email might have been sent out from the system? To be on the safe side I have changed my password and updated all plugins and WordPress core to see if that helps. My main concern is if something like user registration plugin is allowing other users to ‘hack’ the system.

Changing the password is a good idea since the job seems to be posted by the admin account. As for how this email got sent, that’s not clear. User registration plugins shouldn’t give access to other users to “hack” the system but I don’t know which plugin are you using or how you have set it up.

If you are using some code customizations it is possible that some of them triggered sending this email.

No, that is not possible.

Hi there!

Can you explain about what access are you trying to restrict? Are you trying to prevent Subscribers from accessing the job posting page?

>Employer posting and editing own jobs

Employers already only have access to their own jobs. What else would you like to restrict?

Hi there!

You can bulk un-expire jobs by picking the jobs and using the bulk Edit action. Then you need to set the status to Published and update the jobs.

The expiry date will be removed from each job and you will have to re-add them one by one.

Hi @amast7 ,

I tried reproducing the error and I see what you mean. It doesn’t seem that the page that gets loaded is random, though. As many times I tried, I got the same job page reloaded.

I checked the page loading using the browser tools, and I see there is something strange happening there.

Please see: https://d.pr/i/GRhsHY.

It seems as you have some kind of trigger on your Careers page that will attempt to load any job page, and it fails each time until it reaches the last one. You have a lot of js code running on that page so I wasn’t able to tell which one could be causing this.

This looks like some kind of a conflict, and I recommend trying to figure out by switching the theme to Twenty-twenty (or any other WP default theme) and disabling other plugins.

Hi David,

You are right, our documentation mentions both locations for saving translation files, wp-content/languages/wp-job-manager/ and wp-content/languages/plugins/wp-job-manager-resumes-LOCALE.mo.

Saving files to either of those locations will work but the wp-content/languages/plugins/wp-job-manager-resumes-LOCALE.mo one is considered as safer. However, if you decide to use a different translation plugin at some point (for example Loco Translate) you will notice that the files saved there don’t get recognized by those plugins. That doesn’t mean WordPress itself won’t recognize them.

As for your original issue, I suspect you have several translation files and since some files get priority while loading, the one that you want to use gets overridden.

For example, if you save wp-job-manager-de_DE.mo files in wp-content/languages/plugins/ as well as in the wp-content/languages/wp-job-manager/, the first one will have priority when loading.

I suggest you try removing the other translation files.

Another possible cause of the problem could be the WordPress language you chose was not the DE_de one (Deutch) but any of the other locales.

Can you share a link to the page that displays differently?

In general, it’s expected for browsers to not display pages the same way and what they do display will mostly depend on the CSS your theme is using.

Hi there!

I checked your site and this looks like some kind of a conflict. Have you tried disabling other plugins to see if any of them could be causing this?
I have noticed some 404 and 403 errors in the browser console that look related to Google tag manager. Not sure that is the cause, but I recommend you check them out first.

OK, so you have copied your files from /public_html/wp to /public_html. That is good, so your files are in place.

Let’s try to solve this migration issue.
First, if you can, backup your existing database.

Next step has to be importing data to the new database. You said that the sql file didn’t get downloaded. You can try to access your site by going directly to https://www.zymatinternational.com/wp/wp-login. If you manage to log in, try to download SQL file again. If you are using some kind of download manager plugin or extension installed in your web browser you will have to disable it first. If you manage to download it, you will have to import it to the new database and then connect that new database to your site located in public_html. You will do that by opening wp-config.php (in public_html directory) and edit database info (db name & password).

If you can’t access your site (that includes Migrate DB plugin), you will have to make changes in database. You can use phpMyAdmin for that. Open your database and find wp-options table. The WordPress Address and Blog Address are stored as siteurl and home (the option_name field). All you have to do is change the option_value field to the correct URL for the records with option_name=’siteurl‘ or option_name=’home‘. That means that you have to find the place where it says https://www.zymatinternational.com/wp and change it to https://www.zymatinternational.com

There are some other steps to complete, but let’s first see if any of this will help you access your site.