I just upgraded 2sxc to 09.08.00 and an app suddenly stopped working.
So what we called in the template was:
data-latitude='#Content.Lat.Replace(",",".")'
data-longitude='#Content.Long.Replace(",",".")'
And that worked fine, but after the upgrade, it does not render the coordinates anymore, so in the source, I can see data-latitude data-longitude but no values.
Any ideas what I should change?
I'm not sure but there was an issue with numbers being zero instead of null when not set, causing side-effects. It will be fixed in 9.10 to be released next week. Please check that first, otherwise post your question again.
Related
Screenshot with SQL? everywhere.
I upgraded to the latest stable version; I tried changing themes; I've tried different hosting servers. These SQL? messages still show up. Sometimes there might only be 4 - 6 on the screen, sometimes, like the screenshot I added, there are so many, you have a hard time seeing your data.
I tried searching the phpliteadmin.org site, and the web using DuckDuckGo, but, as you can imagine, searching with the term "SQL?" gives you thousands of useless pages to sift through.
I can't be the only one who has this issue, so I'm sure someone has figured out what the problem is, right???
Thanks muchly!!
Even if this question is 9 month old, i stumbled upon it while having the same issue - finally finding the solution to this:
The "SQL?"-outputs are just debug-information!
You can opt-out them in your phpliteadmin.config.php by changing
$debug = true;
into
$debug = false;
THIS is not a duplicate question!
In my app, I have collections directory (in project root) with files (every file corresponds to one collection). My tempates (in client/templates/...), of course, use collections. Everything perfect with one small exception. One of my collections is undefined but the rest is ok. Every collection is defined in the same directory and in the same directory level. Where is the problem?
EDIT: I tryed inserting collections inside lib. Not works. I tryed deep nesting. Not works.
EDIT: Tell me, why I have 2 downvotes. Downvotes are for good for nothing questions, this question may help in future another Meteor users. So, why are you downvoting this quetion?
Bug has interesting roots. I'm using fedora 21, and in theese times, Chrome has bug which causes complete freeze (1-5 hours). This bug has many Linux distributions. After I restarted chrome after freeze, the error vanished. So, the result is that Chrome has two bugs instead of one :)
EDIT: No. It's premature conclusion. It works only for a while but then it failed again. In Chrome and in Firefox too. I'm really confused.
I've got a single meta variable with a string value that should always be 0 or 1 being stored on pages. I can set it using a simple dropdown box in a metabox and it seems to work great. For some bizarre reason, it sometimes gets changed from 1 to 0 seemingly randomly. I have no clue why, and it seems to happen even on a page I wasn't editing or updating. I'm baffled and don't even know where to begin looking because I haven't figured out how to replicate the problem.
Does anyone have any suggestions to search for a possible way to replicate this or figure out the cause?
IMO: That kind of bugs only can be catch debugging. Exists a tool called mtop that allows you see at all DB actions...
UPDATE
More easy is to log all queries in a period of time (until you see the malfunction) Here a related issue: Log all queries in mysql. Then you only need to look closer at update actions in the appropriate table. This can be done in windows or *nix. Good luck...
Just wondering if any one might now how to fix this issue.
Every part of the databroker is created and also all the database connectivity is functional.
But once we try to place them together we come up with a error saying cannot create Null Databroker.
The thing that is really strange is that we have databrokers that are basicly the exact same working.
Can any one shine some light on this issue?
We worked on this together today. We did three things to troubleshoot and fix the problem:
we changed the calling workflow so that the dataset is refreshed inside the show-screen tags (previously, this was done before the screen was called).
we refreshed the dataset (a H2 db) and connected the database (before, it showed as pool not open)
we changed the database name to main
It is working now.
"Null databroker" suggests that the broker was not created correctly, although it doesn't look like that was the case since you don't mention having to modify it to get it to work.
In these cases it can be useful to look at the error logs through the admin app to see if there are errors being thrown at some time other than compile time.
We're running on .NET 3.5 SP1.
Recently, in IE, some of our users started getting "Out of Memory" errors once in a while. This doesn't happen all the time. I managed to replicate it a couple times and I found that this code, from the AjaxControlToolkit.Common.Common.js file, was causing an infinite loop:
AjaxControlToolkit.TextBoxWrapper.registerClass('AjaxControlToolkit.TextBoxWrapper',
Sys.UI.Behavior);AjaxControlToolkit.TextBoxWrapper.validatorGetValue =
function(id) {
var control = $get(id);if (control && control.AjaxControlToolkitTextBoxWrapper)
{
return control.AjaxControlToolkitTextBoxWrapper.get_Value();}
return AjaxControlToolkit.TextBoxWrapper._originalValidatorGetValue(id);}
The last line (which calls _originalValidatorGetValue) basically calls back this exact function over and over because control.AjaxControlToolkitTextBoxWrapper is undefined.
The function defined right above it is AjaxControlToolkit.TextBoxWrapper.get_Wrapper(control) and could be use to create the wrapper if it doesn't exist, but I don't get the feeling I want to be changing the framework if I'm the only one who's seen this bug in the wild.
The bug does not always occur. It seems to occur when the first URL that is loaded contains an AJAX history point. If you open up a page and play with it, causing history points to be added, it works fine. But if you copy-paste the URL into another browser windows, you will get this problem.
Therefore, my guess is I am doing something wrong with the history control that doesn't setup the wrappers properly. Even so, there appears to be an infinite loop in there.
Any ideas/clues?
I filled out a bug report on Microsoft Connect. While filling it out and testing various scenarios, I noticed it was working fine locally but not remotely. Comparing my production/development environment, I noticed CombineScripts was false locally. Deploying that to my production server seems to have resolved the issue.
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=373171
If you remove LoadScriptsBeforeUI='false' from ScriptManager, this problem is solved.
You might want to post a bug report on Microsoft Connect.