I'm using drupal commerce and I added a new product (and product display).
I can see it in the listing, but when a user click on the product page, it's saying : permission denied.
All the other products works fine, it's only the last one which doesn't.
I tried to rebuild the permissions but that doesn't changed anything. How can I check what is "denying" the page ?
The Access denied backtrace module should help you
I found that for drupal 7, the devel module as a submodule called developper node access which shows exactly what I want. For this you need first to enable it and the active the access by user block. This block shows for every users if the current node is accessible and if not why (i.e. which module is denying it).
If your using Apache you might as well look at your .htaccess configurations. I faced a similar issue in the past and by using appropriate permission in the .htaccess file everything fell in place.
Refer http://www.digitalocean.com/community/tutorials/how-to-use-the-htaccess-file to learn more about configuring .htaccess file
Related
I have activated a Two Factor Authentication sing in method called "Clef" on my WordPress based site. It turns out they have shut "Clef" down on July 2017.
The problem is that when I want to sign in to my WordPress dashboard, I get a "loading clef login" page and nothing happens.
How can I remove it?
As promised, here are the steps you could take:
Option A:
Download FileZilla
Log in, using the Login Credentials supplied by your Registrar/Hosting Provide
Go to: /httpdocs/wp-content/plugins
If /httpsdocs/ is not there, simply head to /wp-content/plugins
Find the name of your Plugin (Presumably 'Clef') and simply delete the Folder.
Option B:
I am not sure who is providing your Domain/Hosting but you can always login via your Domain/Hosting Control Panel and delete the Folder from the Web files, that way.
If I were you, stick to Option A. Not only is it the most universal but something I would advise getting an understanding for, since you could use FileZilla to backup your Web Files in the future.
Any problems, drop me a Comment and I will help you along the way, if needs.
The easiest (and possibly the only) way will be going to the FTP server, going to wp-content/plugins/ directory and removing clef directory (or whatever is the name of this plugins directory name).
WordPress will disable this plugin automatically, if it doesn't exist anymore.
So I've been trying to get into the admin dashboard for a WordPress website that I'm supposed to be working on and for some reason my XAMPP/phpMyAdmin & Avada theme does not seem to be working properly.
When I configured XAMPP it worked fine and could reach the admin dashboard without any issues. But when I replaced the WordPress directory downloaded from the network admin and the .sql database table uploaded into phpMyAdmin I am now noticing that when I access localhost/wp/ it loads a broken page, appears to be missing the CSS (styles/images)
I've tried to navigate to locahost/wp/wp-admin/admin.php and /wp-admin/login.php and I am not able to load the files I continue to receive a "File not found" redir error.
In my own opinion it seems as though the user isn't entirely authenticated and is causing me to redir based on failed authentications OR the system is having difficulties with the folder structure to determine the areas for the "missing" wp-admin files, although I have confirmed they are physically residing within that expected location which only further confuses me.
I can upload and attach any type of document, just let me know what type of information you are looking for to assist in troubleshooting.
THANKS FOR ANY AND ALL HELP!
1) Ask wp questions at wordpress.stackexchange.com
2) you may have problems with .htaccess and .sql file permalinks. Ask people at the mentioned forum.
Step 1 : Remove htaccess file from your root folder
Step 2 : check wp_option table and change site_url and home_url
Step 3 : Login into wp-admin using
http://localhost:8080/mysite/wp-admin/
Step 4 Goto setting ->paramlink and update using custom structure.
That's it.Problem solve.
I was just working on a Wordpress site and after updating a plug-in (which had not yet been activated, only installed) I activated it. Instead of the activation working, it gave me this error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete >your request.
Please contact the server administrator, webmaster#ibsmithmedia.com and inform them of >the time the error occurred, and anything you might have done that may have caused the >error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an >ErrorDocument to handle the request.
I am getting this error on every page of my wordpress site, not just the plugin page or my user admin area.
How can I fix this? Is there a way to undo this plugin activation (I'm pretty sure it's what's causing the issue).
I don't have access to the actual FTP files of the site, I'm working on it for a friend. But I can get access if that's the only way to fix this. Thanks!
I would get access and delete the plugin.
That would be the fastest solution.
I ended up having to delete the folder for the plugin and then going to my htaccess file and remove extra lines that the plugin had added there as well. That resolved the issue.
First you need to connect to your website using FTP client, or File Manager in cPanel. Once connected, you need to navigate to the /wp-content/ folder.
Inside wp-content folder, you will see a folder called plugins. This is where WordPress stores all plugins installed on your website.
Right click on the plugins folder and select Rename. Change the name of the plugins folder to anything that you like. In our example, we will call it “plugins.deactivate”. Once you do this, all of your plugins will be deactivated.
Usually, this method is used when you are locked out of your admin area. If the issue was with your plugins, then you should be able login to your WordPress admin area.
Once you do that, go back to your /wp-content/ folder and rename “plugins.deactivate” back to plugins.
Now you can activate one plugin at a time until your site breaks again. At which point, you will know exactly which plugin caused the issue.
I am developing my own plugin.
Under my plugin's directory I have a file called migrate.php. I would like to be able to navigate to this page, without having it be in the left menu.
When I go to
admin.php?page=myplugin/migrate.php
// ERROR: You do not have sufficient permissions to access this page.
How can I grant permission to the administrator to view this page ?
My guess is that the page view is failing because the slug you are using isn't defined as a slug (ie by being added as a menu or submenu).
You could work around this by calling the PHP file directly, but then you'd need to include the WordPress loader to load the WordPress environment.
Hope this gets you a little closer ...
I have a Drupal site and the Drupal site's admin is not able to access the edit views page.
Lately, the site has also had the problem of Content Access permissions which required me to rebuild the permissions.However, the warning that 'Content Access Permissions need to be rebuilt' continues to persist.
Whenever I goto admin>build>views page, it redirects me back to admin>build page.
Could it be a problem of content access permissions? Should I rebuild it? Would it solve the problem.Its a cumbersome process and many a times, the permissions are not built properly so I was hoping to avoid it. Is there another way of doing it than through the admin console.
When you get redirected back to the build, it's because the path doesn't exist.
In Drupal when you go to admin/build/views, it try
admin/build/views
admin/build
admin
The problem is that views isn't installed, or that you need to clear the menu cache, which can be done at admin/settings/performance. If you needed permission, you would get an access denied page instead.
This happened to me, because somehow my views UI got disabled. I enabled it again on the module page and problem solved.