I am using WordPress with Jupiter Theme. I have just updated the Jupiter theme with the latest version. The website is working fine but there is a one-page show Warning in the location of the header. The warning is:
"Warning: include_once(): Failed opening
'/srv/users/serverpilot/apps/inj/public/wp-content/themes/jupiter/framework/admin/control-panel/logic/icon-selector.php'
for inclusion (include_path='.:/opt/sp/php7.1/lib/php') in
/srv/users/serverpilot/apps/inj/public/wp-content/themes/jupiter/functions.php
on line 263"
When I check the location of the missing file icon-selector.php, there is no icon-selector.php located there. I have one icon-selector.php file from my old version, so I copy and paste the file to …admin/control-panel/logic this location, however, the warning is still there.
Any thought to remove the warning?
It might be related to Jupiter's new control panel. However, make sure you have installed the theme and its plugin properly also it's better to contact the Jupiter author.
Related
I'm using blogdown and Hugo to generate a website.
I've created a new R project and have downloaded the theme using:
blogdown::new_site(dir = "Theme", theme = 'pacollins/hugo-future-imperfect-slim') and I can preview the template once downloaded. However, if I close R and then restart and I use the add-in "serve site" I get the following error message:
Error in site_root(config) :
Could not find config.toml / config.yaml under...
and then the directory that the config.toml file is saved in (and all of the rest of the theme files) are listed.
I can't understand what's changing between being able to preview the site in R Studio Viewer, then quitting R and restarting and it not being able to find the config file.
I did find this advice: https://github.com/rstudio/blogdown/issues/48 which suggests that my working directory is not the root directory of the website. There are two things I don't understand:
1) How can the the root directory and working directory work together okay when I initially download the theme, until I quit R and restart, and then they appear to not be the same?
2) How to I change the root directory of the website to fix the issue?
Thanks!
If you followed the blogdown's documentation to create a new site with the command "blogdown::new_site(dir="/your/website/dir")", it will set your working directory to "/your/website/dir".
When you restart R/Rstudio, your current working directory is reset (probably to your home directory). You can check the current working directory with getwd().
The solution is simply set up the working directory:
The simpler way is to execute setwd("/your/website/dir"), then you should be able to run blogdown::serve_site()
The recommended way is to create a Rstudio project at /your/website/dir with File-New Project-Existing Directory. It will create a .Rproj file under the root directory of your website. After that, you can "open project" and work on your website, then preview with serve_site().
i am using WP Quick Install Script to install WordPress and it works fine. but it's not installing my custom theme. i also placed theme as theme.zip in WP-quick-install folder but it shows a white blank screen on front-end.
what is wrong there?
Any reason why you are using WP Quick Install in the first place?
I would simply suggest setting up the site as normal and adding your theme into the /themes/ directory.
If this is daunting, just shout, but first read the Wordpress Codex - Installing Wordpress
Symptom:
When I start a new post on my Wordpress (example: http://website.com/wp-admin/post-new.php), I have the following problems:
The tinyMCE editing toolbar is missing, and
Text does not appear when typed in the body of the new post
Attempts:
Following Wordpress' guidelines, I tried the following without success:
Deactivate all plugins -- still no edit toolbar.
Use other browsers -- same error in Chrome, Firefox, and IE on multiple machines.
Enable SCRIPT_DEBUG in wp-config.php -- same error.
Viewing browser errors in Chrome -- see below.
I opened Developer Tools ("F12") in Chrome on the new post page and found the following 3 errors:
Failed to load resource: the server responded with a status of 404 (Not Found) -- [wordpress-website]/wp-includes/js/tinymce/tiny_mce.js?ver=349-20805
Uncaught ReferenceError: tinyMCE is not defined -- wp-langs-en.js:1
Uncaught ReferenceError: tinyMCE is not defined -- post-new.php:760
Question:
What must I do to get the edit toolbar back?
404 errors are an indication files may be missing. Have you verified the files haven't accidentally been moved or deleted?
You can replace the contents of the wp-includes/ directory where TinyMCE is located. You can either do this via the admin area updater, or you can do it manually.
Automatic way
Log into your WordPress admin area
Navigate to Home > Updates
Click the Re-install Now button
Manual way
Download a copy of the version of WordPress you are currently
running (if you are not running the current version you can find a copy in the release archive)
FTP into your site
Make a backup of your wp-content/ directory
Delete the wp-includes/ directory from the server
Upload the entire wp-includes/ directory from the new copy of WordPress you downloaded
You should now have a completely replaced wp-content/ directory and all of the TinyMCE files will be on your server.
I followed the instructions for installing Django CMS on my mac. When I run "manage.py cms check", everything is fine, except it says it cannot find the template_1.html. When I go into the admin to create a page, the template is in the Template drop down. When I try to save the page it gives me "TemplateDoesNotExist at /admin/cms/page/add/".
Maybe it's noteworthy, I was having issues with the url prior to this error. I was not able to open the admin or even get main page to render in the browser. After searching stack overflow I found the same issue. I changed the url patterns from the "urlpatterns = i18n_patterns" to the standard. That worked. Now I have this issue. Any assistance would be appreciated. Thanks.
Link to Traceback if needed:
http://dpaste.com/hold/1430437/
I had the same error (on Ubuntu 12.04)
Following the django-cms 2.4.3 installation instruction,
django-admin.py startproject myproject
creates a directory myproject (in which manage.py resides) and a subdirectory, also named myproject, which contains the setting files and the templates directory.
I don't know if this is the intention of the authors of the django-cms doc. But the instruction
os.path.join(PROJECT_PATH, "templates"),
in the TEMPLATE_DIRS setting points to /absolute/path/to/myproject/templates.
This should be changed to:
os.path.join(PROJECT_PATH, "myproject/templates"),
to point to the correct directory /absolute/path/to/myproject/myproject/templates
I followed instruction as mentioned in Wordpress, but I still got the error and referred Google and I was shocked to see many blog have same problem and they are not fixed yet and those blogs are indexed in Google, please try searching "Call to undefined function require_wp_db()" or find here
Google search result
Any advice how to fix? Thanks in advance
This will occasionally occur if you do not upload wp-config.php or all of the other files that have changed between versions.
Download a clean copy of the WP version you are trying to upgrade from the WP Release Archive.
Update wp-config.php with your database details, secret keys, etc.
Delete all files except for /wp-content on your server (hopefully you have kept all of your custom enhancements relegated to the /wp-content/themes directory as they recommend - otherwise you will have to diff against each individual file unless you've kept good track of your changes).
Upload all of the clean files except for the /wp-content directory
Run /wp-admin/upgrade.php
This question might have been misplaced on this site, but the cause of this error could be a general programming bumble.
Your problem could stem from ambiguous include paths. When using include / require / include_once / etc... if the filepath is not absolute, the file that gets included might not be the one intended. Read why here. To fix an ambiguous include directive, prefix the relative path with dirname(__FILE__).'/'.
A plugin or even your theme could be the culprit. A regex like this could help you find cases of this: (include|require)(\_once)?\s*\(?\s['"][^\/]
Example
I had a Wordpress theme for a multisite install that included a file like so:
require_once('sites.php'); Because sites.php was a file in the same directory, (and because the server's include path included "." -- the current directory), it worked.
However, because sites.php also existed at /wp-admin/network/sites.php, so this line caused the following error when trying to access the network dashboard:
Fatal error: Call to undefined function _get_list_table() in /www/OCE/WEBEDITOR2/wp-admin/network/sites.php on line 19
After trying the instructions in the other answer to no avail, I fixed my problem by finding and changing this line to:
require_once( dirname(__FILE__).'/sites.php' );
Note: In most, cases, Mark's suggested solution should be employed first in trying to fix this error after upgrading Wordpress, if only to eliminate other possible issues.