Am working on a drupal-7 site but it suddenly has stopped showing the correct theme and just shows a garbled UI.
have thought about it and cannot seem to locate the reason for this.
wanted to ask that if any suggestions can be given of this . secondly is there a way to refresh the drupal site (i.e. run the drupal site installation process again without re-installing/deleting any physical file/database).
hope to have made the question clear :)
Two common reasons.
The last thing you did broke it.
Someone hacked it.
Reinstall the exact same version of drupal in a new folder with a new empty database. If the only things you changed were the content (no PHP patches etc), then you should be able to simply switch databases. You could also diff the installations to see if any files were altered.
issue solved. problem came apparently from a module (custom made) which had function name same as used somewhere else on site.
thank you for time and suggestions
Related
We have a DNN site and I noticed on our home page that the dev tools show an error with an events.js file that is trying to call "analytics.tiktok.com". It is being blocked. I don't know if this is purposeful and I've searched our DNN modules code but haven't found an such reference.
The other devs can confirm they haven't added such code. I've searched the code folders for a file named events.js but haven't found one. I'm aware that DNN has large portions of it that are data driven but I don't know what tables to query to see if there's code that has that URL.
Is anyone aware if DNN or kendo controls has an references to tiktok?
It is definitely not part of DNN.
Another place to look for these calls are the skin (theme) controls in use, or the default.aspx. Anyway, if no one is aware of this stuff, I would check if you have a security hole (old Telerik libraries, unsafe passwords in FTP accounts...)
I would start by looking at the location in which that is embedded into the source of your webpage. Depending on where it is, that might help you track down "where" it is coming from.
It could be coming from inside source for a module, in the content of a module, in module settings, in a container, in a skin/theme, etc.
I used to connect my Salesforce projects without any problem since today.
Now everytime I want to create or open a new project through Mavensmate. I get this error :
Error initializing project: client identifier invalid
I don't know how to solve it. I have googling without finding any solution. I thought this could solve my issue, but it doesn't work.
Please help!
Not sure if this is related or already said but it sounds like MavensMate has finally died. Related conversation/details here. If I knew how to build the windows version of the MavensMate source I'd try myself but seems like there is a security issue that would have to be applied too which I don't have time for (plus possibly out of my expertise reach).
So I'm now biting the bullet and starting the move from Sublime to VS Code using a couple different articles (here and here). Pretty sad about this but seems no other way. If possible I'll loop back to Sublime in the future but no idea if that will be feasible or not. If anyone finds a fix for MavensMate or a new way to do SFDC work in Sublime please let us know!
I've been following the tutorial videos for DotNetNuke and i am at the part where i am now creating my own modules. I've installed everything i need to and put the template in the required folder, but whenever i try to create a project it comess up saying
"The local IIS URL http://dnndev/desktopmodules/... specified for Web project ... has not been configured"
It then asks me to create a virtual directory but says i cant because the server "http://dnndev" is not on the local machine.
I've searched for answers for a while now and have tried editing the template file and the host file but no matter what i try i always get the same message back. Does anyone know how i can fix this?
Thanks
If you follow these steps for setting up your Development environment than the templates should work as is.
http://www.dotnetnuke.com/Resources/Wiki/Page/development-environment.aspx
If you are using a different path for your website I would recommend customizing the templates.
http://www.dotnetnuke.com/Resources/Wiki/Page/Customize-Project-Template.aspx
I assume you are using dotnetnuke wiki page link which seems confusing. For better steps go to: http://www.dotnetnuke.com/Resources/Blogs/BlogID/16.aspx and locate "Let's Build a Module #1 - Project Introduction" which is a first video in step by step series of videos which will help you to clearly understand the process.
Let me know if you need more help.
i am new to drupal and it is irritating me. i have mastered wordpress and SMF forum software to a near expert level. but drupal as well as joomla have made the admin interfaces so totally confusing i wish there was an answer available for me to use and drop them altogether.
i cant get the slide show to show up on the front page or any other page. i cant find in there a sufficient means of manipulating the content blocks and logging and nav blocks. i am not new to computers and programming, and if this was a programming problem, i probably would have fixed it by now, but the interface is so confusing i cant get the site to do anything im wanting it to do.
i have looked at several tutorials that dont help at all. i found out about a part time job my company is offering and i know for fact i can do it if i can get past the fact that the admin interface is a maze of confusion.
theme demo - http://adaptivethemes.com/demos/atcommerce/
my test - http://tse.myfewclicks.com/drupal/
i beg anyone willing to help. i need to have something presentable, at least a good taste by monday. i could have already been done with it with SMF or wordpress, but they are the wrong type of software for the job.
please help someone.
It would appear that you may have solved your problem. I followed your link and the image rotator was working.
About the only difference was that on the AT demo site I was able to click the dots at the lower right hand corner to select the image I wanted whereas on your test site I was unable to do so.
I am working on my first DotNetNuke website and there is a requirement for all the custom module functionality I am developing to be available with JavaScript disabled.
However, when I create a module that contains a simple submit button, i.e.<input type="submit" />, DotNetNuke displays a critical error with JavaScript turned off but works as expected with JavaScript turned on.
When I attach to the running process using Visual Studio, the unhandled exception is thrown from admin/Skins/Nav.ascx.vb line 177. The inner exception message is "Invalid JSON primitive: ."
My research online only managed to turn up this forum post (Postbacks are not working when Javascript is disabled in the browser) that appears to be the same problem as mine, but no solution is provided.
Can anyone shed any light on this issue? Is it viable to be attempting to write non-JavaScript functionality in this version of DotNetNuke?
Update: it turns out that another website designed recently with Dot Net Nuke by the company I am working for is having the same problem with non-javascript postbacks when using DNN version 5.1.4 but it does not have the problem (i.e. it can postback without javascript) in DNN version 5.0.1.
So perhaps a hard dependency on javascript has been introduced at some point after version 5.0.1. We are investigating this possibility further and I will keep this question updated as we go. Obviously I still welcome anyone's input on the subject.
Update: i've started a thread on the Dot Net Nuke forums to see if I can get any help there. If any solutions come up I'll post them here. Trying to find official DNN stance on support for javascript disabled functionality
One of the developers in the office found a workaround to get postbacks working with javascript disabled. Unfortunately since he does not have a Stack Overflow account, I will try to translate his solution as best I can for those who are interested. Bottom line is postbacks with Javascript disabled is possible once you make a few changes to the Dot Net Nuke environment.
Step 1 - Change the menu module. In our case we used the Telerik RadMenu.
<dnn:NAV runat="server" id="dnnNAV" ProviderName="DNNMenuNavigationProvider" IndicateChildren="false" ControlOrientation="Horizontal" CSSControl="mainMenu" />
becomes
<dnn:RADMENU runat="server" id="dnnRADMENU" MaxLevel="2" EnablePageIcons="False" PagesToExclude="" ShowPath="True" />
Step 2 - Remove the actions and visibility modules.
<dnn:ACTIONS runat="server" id="dnnACTIONS" ProviderName="DNNMenuNavigationProvider" ExpandDepth="1" PopulateNodesFromClient="True" />
<dnn:VISIBILITY runat="server" id="dnnVISIBILITY" minicon="images/DNN-minus.gif" maxicon="images/DNN-plus.gif" />
Step 3 - Download the DNN source and make two changes in the LibraryUI\Utilities\ClientAPI.vb file.
Line 155:
DotNetNuke.UI.Utilities.ClientAPI.RegisterClientReference(objButton.Page, DotNetNuke.UI.Utilities.ClientAPI.ClientNamespaceReferences.dnn_dom)
becomes
If Not objButton.Page.IsPostBack Then
DotNetNuke.UI.Utilities.ClientAPI.RegisterClientReference(objButton.Page, DotNetNuke.UI.Utilities.ClientAPI.ClientNamespaceReferences.dnn_dom)
End If
Line 355:
ClientAPI.GetCallbackEventReference(objPage, "", "", "", "")
becomes
If Not objPage.IsPostBack Then
ClientAPI.GetCallbackEventReference(objPage, "", "", "", "")
End If
Step 4 - compile the Dot Net Nuke library.
Note: Also make sure you are not logged in as an admin or host, as the admin/host panel at the top of the page will also break if you attempt to postback with javascript disabled.
Hope this helps someone else. If you feel like I'm missing some important details, let me know and I'll try and fill in what's needed.
DotNetNuke relies heavily on JavaScript and I doubt there is a real easy way around it - at least considering you need to support all functionality. Perhaps you can clarify that?
The the bottom line here is that you're going to need to modify DotNetNuke to meet your needs. It certainly isn't impossible to get it working, but I would venture a guess that it just plain isn't worth it for most people.
If, as you said, you need to retain ALL functionality without using JavaScript, you're going to have a pretty substantial amount of work to do.
I'd suggest, to get started, you download the source package, set up a development environment on your local machine, turn off JavaScript in your browser and start taking notes. This will help to determine the level of effort involved.
I'm guessing you won't get a lot of responses out of this one (as the poster in the forum thread you linked to didn't) as very few people have sat down in front of DotNetNuke with this as a requirement.
Also, keep in mind that any time you're making substantial changes to the DotNetNuke framework, you're interfering with your ability to easily perform upgrades in the future. Just another thing to think about.
I believe that I've seen the leadership in DNN say that they've taken a hard dependency on JavaScript, and have no intention at this time of considering a non-JavaScript compatible scenario.
That being said, being able to do a simple postback shouldn't be too difficult to support. I would look around in the Client API area for the error that you're describing. A lot of the Client API code is in the DotNetNuke.WebUtility assembly, which is a separate download from CodePlex to get the source.