Somehow my DNN has a broken path a particular url serves pages, but doesn't work for delete or advanced options (delivers a 404 error)
The taburls table has no entries for this tab.
If I change the url through the tabs table then I'm able to delete the page without issue.
I tried accessing the page options via tabid, but the tabid gets converted to the friendly name and then 404s.
I tried turning off friendly urls in my web.config but I may have done it wrong since the entire site would not load (yellowscreen of death)
I'm wondering where DNN is storing this path that is breaking the advanced options of whatever page is at the path.
How do I fix this url so it displays page options and lets me delete pages?
First thing I would try is going to the Admin/Page Management screen, can you make the changes you need to via that interface? If so, after making the changes, are you able to access the page and all the features/options correctly?
If that doesn't work, check the TabPath column in the TABS table to see if there are any bad paths in there for specific pages that you are having problems with.
Related
I'm looking to edit Drupal's admin pages.
Some of the things I'm trying to achieve:
Remove is the the filter setting on the Content page/node/view. In other words, if I go to to the Content page and I filter by a certain type of node, then I leave that page, then come back, the filter setting is saved, I'd like it to reset each time I visit the Content page.
I would like to modify some of links associated with these pages, as an example on that Same Content page, the titles of the pages are linked to their 'front-end' views, I'd rather have them link to their 'edit' screens.
While I have been successful in modifying the front-end theme of Drupal, by editing the actual php files. I can't find the the same php files for the Admin theme. In our case we are using Seven (7.21). I've read something about views, and thought maybe the entire Admin theme is built as views, aka there no php files involved like the front-end theme has, but under the Views section I did not find any either. I'm still pretty new at this and coming from the Wordpress world, this is a Drupal is a lot different.
The logic for that section of the admin area is at (from the public root):
/modules/node
Specifically "node.admin.inc"
That being said, I don't recommend editing core scripts, as they will be overwritten when you update the core.
You could explore making your own module to supplement that page, or your own view or explore some pre-made modules, such as "Admin Views"
Find de view displayed and go to its configuration :
1 - Edit configuration view like suggested here : https://drupal.stackexchange.com/questions/44440/how-to-remember-exposed-filter-choices
2 - Rewrite output views to rewrite link : field https://www.drupal.org/node/1578524
Another option is to create and use your own dashboard/views to achive like you want http://definitivedrupal.org/suggestions/creating-custom-administrator-view-content
also you can see contrib module : https://www.drupal.org/project/admin_views
You don't have to use that default content overview page at all. Make your own instead:
Make a page view (you have to install views module if you already did not: https://www.drupal.org/project/views) and use table layout. Make sure that page paths starts with "admin" so it will use admin theme. Also pay attention about permissions, so only specific set of users (admins) can use it.
For that view you can freely select what columns you what to show. You can also allow ordering by any column and action if you click on some field.
Use exposed filters to add filtering form, again add any filters you need. You can even set the form to use AJAX, to do auto-submit when some filter field is changed, include reset button and more. Also for every exposed filed you can select (at fields settings) should it remember it's value or not.
At end, edit admin menu and add your new page to it so it will look and act as default one but will offer much more functionality. You can even totally remove default one from the admin menu.
Views module is very powerful, not only for front-end but also for back-end content handling.
I am new to DNN and I'm trying to make a site with custom skin.
Skinning is all ok but once the superuser is time out, I couldn't login again.
The login page has disappeared and was being redirected to an empty custom skin page which only shows the header and the footer.
I have tried
localhost:1234/login
localhost:1234/admin
localhost:1234/?ctl=
but neither of them are working.
I tried to search for solutions but none of them seems to work and not relating.
Please show me a way, if I am missing somethings.
You might look at the Admin/Event Viewer page if you happen to still be logged in somehow (or eventlog table in the database) to see if there is an error being thrown, that isn't being displayed (because you aren't logged in).
That may point to the problem.
You might have a problem with a "container" that is missing thus the module isn't being loaded.
A few other things to try, try
localhost:1234/?ctl=login
localhost:1234/?ctl=register
See if anything loads for those.
Last resort, go into the database and NULL out the SKinSRC columns on the TABS table and see if you can find the default site Skin setting in the PortalSettings and make that null or something other than your custom skin.
I'm a complete COMPLETE noob at Drupal.
I've been handed a large very customized Drupal 7 site after our admin quit. I have tons of WP experience, but zilch in Drupal.
I've been asked to edit a page that exists at:
http://my.drupalsite.com/[page]
The page functions only to redirect to:
http://my.othersite.com/
But, I need to change part of the way it redirects. Normally (as in, the one other time I did it) to edit a Drupal page, I just go to the page logged in as an admin and click "edit". Since this is a redirect page, I can't really do this. The /admin/content section has 83 pages of 25 items each with no way for me to search on anything and no way to tell from what the guy called the page as to what page actually does this redirect. I'll be a monkey's uncle if I'm going to click on every darn one of them and then click the "URL path settings" tab at the bottom to see which one of these suckers is the page I'm after.
Surely this is simple for even a typical Drupal novice... like I said though, complete noob.
Any ideas? Thanks!
There are a few modules that can handle redirection or even simple editing of a path.
You can look at pathauto
https://drupal.org/project/pathauto
On that page you should find other recommendations such as the Global Redirect & Redirect modules. I'm pretty sure some of these modules will simplify your task. You should be able to take an existing path and redirect it to wherever you wish, without having to dig in each URL alias on the node edit page.
It's always difficult to give specific advice without knowing more, but , for instance, Pathauto can help you change the path of a specific content type to a specific pattern. That can come very handy if you need to change a bunch of pages with a similar structure.
I am integrating phpList into my website. I initialized database.
I was able to integrate my website with phpList.
In admin panel whenever i try to do anything like delete member from subscriber list or change any setting for subscriber page. I am getting this error "The requested URL /index.php was not found on this server."
I know that this is the problem of path.
When user receives email it says to confirm click on this.
http://admin.ridesharebuddy.com/lists/?p=preferences&uid=TOKEN
When user clicks on this, it displays error page not found.
Because path should be something like this.
http://admin.ridesharebuddy.com/rideshare/lists/?p=preferences&uid=TOKEN
How can i change this path ?
So from what I see, you have 2 issues:
Firstly:
index.php is not being found.
This is generally because of a) an upload error, or b) missing directory traversals within the script (../../ etc..)
What we need to know is why index.php is not found, and why it is being called when you try to make a change
Secondly:
The link generated when the email is sent, is incorrect. This will just be a case of finding where the link is generated, and modifying it to generate a correct code.
If you could update the post with source for the files, then I may be able to help you further.
If you feel you can't do the above, then I suggest using a different, more mature (and better coded), mailing script for your site.
I have a site that I run off the back of another site. In order to save on hosting etc. the domain points to a script and depending on the url that is in the address bar it redirects accordingly to a subfolder which holds the separate sites. I am happy with this and it works a treat. So when it hits url 1 it goes to "www.domain1.com/url1/Home/Index" and when number 2 is typed in it goes to "www.domain2.com/url2/Home/Index". url1 and url2 being the subfolders.
The problem comes when i am developing another site that is going off the back of the original. i have the site developed in vs and am about to release and obviously all of the image urls, script urls etc are completely wrong as they don't take into account the subfolder within the site. they all used /images/site/image1.jpg etc. this means that they are looking from the root and not from my subfolder url.
is there a simple way of implementing this so that i can develop it using vs and not have to change every image reference every time i release code?
i realise this probably has an incredibly easy answer to my problem - i just can't seem to find anything that fits.
Any suggestions?
slight addition to this - when my site loads it loads to the default page - and therefore when i use ../images/site etc this works when the url contains Home/Index, but not when it hits it on the default url which doesn't include the folder and page qualification.
Just noticed this was left unanswered. When referencing in MVC you need to use the tilde (~) to reference the route of the application. So in my instance i have two sites and using the tilde notation if referenced the route of the application, of which each were specified as different routes.