Why MobileFrontend MediaWiki extension doesn't display Main Page? - mobile

I've installed MediaWiki, enabled short URLs there and added Interwiki and MobileFrontend extensions. But MobileFrontend extension doesn't show the Main Page - the output is just empty. The real page is not empty. At the same time MobileFrontend correctly displays other pages (see for example this page).
What could be wrong with my setup?

There is a HTTP code 500 on the main page (Internal Server Error). The server logs are often a good idea to start debugging.

Related

How to migrate an online angular script to local server?

Hi I'm trying to make an offline version of this page:
https://u-he.com/tools/microtuning/ the script is writtin with Angular JS how do I do that?
I saved the page control-s and copied the file to the local server I'm running.
And then I browsed the local ip. the page opened but I get repeated notes ng-repeat shows up as multiple boxes instead of 1 box that edits the same note but in different octaves.
How do I solve this problem please.
You can inspect the front-end code in your browser console. In Firefox it's in the section called "Debugger", in Chrome it's called "Sources". If you use Safari, you need to enable Developer mode first.
Once you have the appropriate view, just click on u-he.com -> tools/microtuning/ -> index
Hopefully it goes without saying that you shouldn't use large swaths of another person's code without at least giving appropriate credit, or better yet getting the developer's permission, unless there is an explicit open-source license.

Why Do I Get a Blank Page on an Error but other people don't

I am watching this video and when an error occurs he gets an actual error on the page and only a blank white screen when he deploys the site.
I see this a few times. However I only see white screen no matter if I am on local host or on production.
I see he is using chrome on Mac and I am using it on PC. Not sure if that is the difference.
While I can't say definitively, my suspicion is that you aren't using create-react-app to setup your project.
You will only see that error message if you have used CRA to set up your project, as that is a specific error handler that is baked into that project. If you're not using create-react-app, React should log an error to your console instead.
ReactJS smart enough to hide the errors to the users when the app is in production mode.
You will see only a blank page if the app gets crashed but if you inspect the page you will see small detail about the error in the console.
if you running the app in development mode you will see full details about the errors.
for this case cames componentDidCatch method to handle app crash errors, instead of the blank page display a “Something went wrong” message to the user or you can send XHR request to the server with the error info.
Check out this example of declaring and using an error boundary
https://reactjs.org/blog/2017/07/26/error-handling-in-react-16.html

Only in Live - Wildcard Custom Redirects not working (BVN 404 handler)

I'm using the BVN 404 handler nuget package to do redirects in my episerver website.
I have a developer, staging and live enviroment.
One of the redirect rules I have is a wild card one. (Box checked)
so for example:
OLD URL: /uk/products/
Should go to the
NEW URL: /uk/services/
as I have the wild card box ticked
/uk/products/productname - Should also be redirected.
This is working in my developer and staging enviroments, but the WILD CARD is not working on our live website.
So on live you only get redirected if the URL is the exact match... So
/uk/products/
that will work and you are redirected. but it only half works in live becuase
/uk/products/productName
is not working in live but is working locally and in our staging enviroment.
I can't work out why, I have checked on the live server to make sure there are no other IIS re-write rules that may be conflicting, I have also made sure we have the same rules in both enviroments, but it still is not working.
Does anyone have any ideas about what could cuase this?
What other things can I check on live?
Any ideas?

How do I make selenium see the network requests made by a web browser?

I have a dotnet Selenium web driver app.
When I'm testing the page one of the things I need to confirm is that a flash object on the page has pulled correct content from a content store on my site. (i.e. the flash object should be loading content from /stuff/info.txt and including that content within the animation.)
As a human looking at this I can use the chrome network tab and see that /stuff/info.txt has been accessed.
How can I make Selenium execute a similar watch and see the network requests made by a web browser?
I did not wrote this, neither tested it however someone did it here: http://www.softwareishard.com/blog/firebug/automate-page-load-performance-testing-with-firebug-and-selenium/
Basically all the requests are exported via netexport and firebug plugins inside a HAR (Http ARchive file)
Please give us your feedback if you give it a try!
Cheers !
I assume you want to automate the process which the developer tools of browsers does. Something like firebug but for verification using Code.
I don't believe Selenium has such features. For now, you will not be able to achieve this.

Cakephp, weird performance issues

I've asked this question all over the web, but nobody has replied so far.
I have a Cake app on a live server. The problem is everything seems to be cached.
Let's say you're on the index page, hit "delete" link to delete a record, and you're redirected back to the index. The "deleted" record is still shown. If you hit the refresh button, the record is no longer shown and the flash message appears.
And it's like this all over the site.
I've disabled caching in config/core.php, sessions are pure cakephp (works the same with database and php sessions), debug is 0.
Server is PHP5.
Any idea is welcome!
What is your browser? I use Opera and I admit it doesn't manage the cache the way I'd want it to. I have to refresh, while Firefox works perfectly (or at least reload the page the way I'd expect it to while I'm debugging)
(from twitter #IvanBernat) have you tried to add meta tag for killing browser cache? use firebug and see if browser get 304 code for your file

Resources