I hope sombody can help me.
I have a really simple webextension with a conentenscript and one backgroundscript (contains some javascript, close tabs and open tabs with specific url). This webextension works fine on my computer but fail on customers and I dont know why because I have the exact same Firefox version (58.0, 32bit), copy & paste the exact same prefs.js in my profile folder and open the exact same url.
So my plan is to log every step in my code to find out how far its going well till it breaks but how can I write my logs to a file in webextension. Just tried the console.log but the logs are gone when my webextension close the tab.
Maybe there are some permission issues or something like that. My webextension is signed and require two permission (access data from all websites and access all tabs).
Related
I experienced an issue for few days now.
On my laptop, before this issue, I was able to open a sharepoint file directly from IE/Edge by typing the url in the address bar and the document was opened in the good app (Word/Excel/PowerPoint) and let me edit it and save to the SharePoint target.
For days now, I'm not anymore able to edit files, when I type the Url on the address bar, a popup appear with 3 choices: Open, Save and Save as.
If I click on "Open", the document is downloaded on a temp folder and I cannot edit it anymore directly to the SharePoint target.
Nothing has been done on the SharePoint server, I still have the contribute access to documents.
I have already changed the option "Open files in the browser" on edge but nothing changed.
I think something has changed on Registry but I cannot found what.
I already test lot of solutions suggested on forums, but now I'm lost.
Someone else has encountered the same issue ? How did you manage it ?
Thank you
I am writing a script that goes to an Amazon URL and clicks on the 'Buy Now' button. That's it. I have to use WebdriverIO, javascript, and ChromeDriver. The problem is that I can't get this button to be clicked no matter which selector I use. I am able to manually do it just fine. But in the Code Inspect below, every combination of div/id/name, span/id/close, or input/id/name has resulted in no clicks. I know the script can see that web object because when I do a BuyNow.getText() to console, it prints out 'Buy Now'. And I know the xpath I use is good because I paste it into Inspect/Find and the exact element lights up yellow. Oh and the .click(), even though Visual Studio Code flags as deprecated, works just fine in previous scripts.
When I manually click on a button, is there a way to see what was the exact element that received this click?
let BuyNow = $(<XPATH>)
BuyNow.click()
Code Inspect
Ok so I found out what the problem was. It had nothing to do with my XPATH selectors, any one of which to the elements in the Code Inspect picture would have worked (example: let BuyNow = *[id='buy-now-button']). The issue is that in the WDIO config file, I had a custom Chrome Profile being used. Which is fine, the Chrome.exe I was using was pointing to another custom Chrome Profile. I thought these two were the same, but the folders paths were getting messed up. Once I resolved them, and had both the Chrome.Exe and WDIO config pointing to the same customer folder, Chrome started to allow me to select buttons. I think that the WDIO code was looking at one user profile of chrome, and the desktop chrome browser that I was using was another user profile.
Solved. Fun Stuff but not really.
We recently upgraded one of our client sites to 09.01.01 to address a Telerik vulnerability, and then had to migrate the site from managed.com to Azure due to manage.com's outage. After the upgrade, a couple of pages on the site have been uneditable using the pencil icon in the persona bar, although the rest work fine. We're aware of the workaround of going into content > pages and clicking the pencil icon there, but even then not all of the areas on the page are editable. For example, there's one instance of the HTML module on the homepage where when you click on its pencil and then click "Edit Content," it just displays a pop-up with the text but no WYSIWYG or way to actually edit. Other instances of the HTML module work fine, on other pages and even other areas of the homepage.
What's more bizarre is that we just spun up another Azure VM and created a dev site from a clone of the live site so we could troubleshoot further, and this problem does NOT occur on that site even though it's an exact copy of the live site files and database and both sites are hosted in Azure.
Does anyone have advice on what might be causing this or how to troubleshoot? My original though was to clone the page and start removing modules one by one to see if anything made a difference, but it doesn't actually remove the module when I click delete. I've read about ways to do this directly in the database, but I'd prefer to avoid that if possible, especially since we're not seeing the same problem on the cloned site.
Thank you!
Could you please see if any error appearing on the logs folder? You can see the logs here. /Portals/_default/logs/2021.02.01.log.resources? The log file name may differ based on website's logging configuration.
A similar thing can be seen from the Personal bar as well using Admin Logs.
I'm a beginner with DotNetNuke and am having trouble debugging this problem. We are using DNN version 5.
On our local development machines our DNN site renders just fine. But we recently deployed to our test server and on there the site only renders fine when logged in as the Host. When viewing the site as just a normal visitor, all the styles are messed up -- it is just a white page with images gone and menus stacked vertically.
Clues / Notes:
We recently added a new .ascx and module
There are javascript errors, but it hard to tell what is causing them
You may ask about the Log Viewer screen. I looked there and I see exceptions, but I think the exceptions there are unrelated ( will look into this)
Works fine in our local dev environment
In server, only renders fine when logged on as Host
What are some steps I can take to try to debug this? Where else can I look besides the Event Viewer to see what is going on here?
Thanks!
What is the "new .ascx" that you deployed? Is that a skin page?
If something is wrong in the skin page and it is the default site page (under Admin > Site Settings), that would explain why non-admin users have issues, but Admin/Host users (where the site's Edit skin is working) don't have issues.
This solved it:
https://stackoverflow.com/a/3831419/614263
Due to permission settings it looks like IIS was blocking requests from the root to javascripts and css files. When looking at the Network traffic in FireFox I noticed that 404 errors were coming from "login.aspx?ReturnURL=../../blahblah.css"
Thanks for all your help and suggestions.
I’ve created a small cakePHP application that uses the auth component to manage an admin section for changes.
The problem I’m having ‘only in the production environment’ is that after I login all I can see is a blank white screen. I should be redirected to a ‘dashboard’ view. This blank screen is also what I get with all other ‘admin’ prefixed views that require a logged in user, thus the auth component.
What is strange about this are two things, (1) this works fine in the local host and (2) this application is a copy of one that works fine in both the local host and production.
What I’ve done to try and resolve this is:
Checked the previous application copy; nothing different found
Checked that the passwords were hashed
Checked that the .htaccess file was uploaded in ASCII format (suggested by the host)
Any help with this is appreciated.
Ideally I’d like to understand how to trouble shoot this type of problem.
Thanks, Prasad
Possible things to do/check...
Turn on debug in your app/config/bootstrap.php file.
Clean out caches in each of the directories in app/tmp/cache.
Make sure you've properly created ACL stuff.
Check contents of app/tmp/logs/error.log and app/tmp/logs/debug.log.
Check /var/log/httpd/error_log (or wherever your web server makes its own logs for errors and php errors).