I try to build a little "social-media-wall" with Joomla 3.4.8. and the "Facebook Wall"-Module (Vers. 8.2) from WebKul.
Example:
On Page 1 I let show the last Post from Rihanna's Facebook-Wall, on Page 2 I let show the last Post from David Guetta's FB-Wall.
It works!!
Now I want to show this two Sites in rotation. Forethat I use a little "Browsershow"-Code. This Code shows this two sites in an iframe. If site 1 ist shown, the Code load/refresh in the background Site 2, and if site 2 is shown, the Code load in the backgroud Site 1.
And now the Problem: On some Desktop-Computers, the browsershow doesnt show the Facebook-Box (only one time directly after the start of the browsershow).
It seems, that the Code cannot load the FB-Box automaticly.
I don't know why. At home, the Box is showing on all Computers (all browsers), but on work, the box is invisible (in all browsers)
Do you have any idea, why? Is there any conflict or problem in the site-code?
Please take a short look at:
http://www.social-studio.de/browsershows/browsershow_2.html
Sorry for my complicated explaining & thank you for help!
Best regards,
Christian
Related
Bit.cloud is not showing my tests, but they are right there, and they show when running bit start locally. Sadly, the link on the no tests page directing me to learn how to add tests goes to a 404.
I the workspace is public, have a look and see here, the first link the is "tests" tab showing empty, https://bit.cloud/koodoo/koomeleon/second-charge/validation/~tests, and this link is a test for the the same component https://bit.cloud/koodoo/koomeleon/second-charge/validation/~code/eligibility/dateOfBirth/index.test.ts.
Also, side note, can I get an invite to the Slack workspace please? Again the link on the bit.cloud page goes to a sign-in page for the workspace bit-dev-community, but there is no way of registering or requesting an invite.
Please and thank you in advanced.
Explanation
The reason your tests are not being show is due to its extension.
Tests are configured to use the .spec.ts extension to work.
Solution
Having said so, rename your test to:
vaidation.spec.tsx
and it will work.
edit: forgot to add the 'x' at the end of '.tsx'
Generally my application response times are good and pages load quickly. However login, using Zend_Auth with mysql db, takes an age compared to other tasks. I'm wondering has anyone else encountered this?
If not can anyone suggest a good way to debug and find the cause of the slow down?
FYI most pages are rendered under a second after their link is clicked whereas login takes around 7 seconds.
First you need to figure out what is causing slowdown. Add this to your application.ini:
resources.db.setDefaultTableAdapter = 1
resources.db.params.profiler.enabled = true
resources.db.params.profiler.class = Zend_Db_Profiler_Firebug
Then use Firefox+Firebug+FirePHP to see (in Firebug Console) list of all queries. Maybe one of them is really slow? Or maybe you make a lot of them?
Other thing to do is to check Net tab (Firebug) with 'keep changes' turned on to see if you don't make too many redirects or maybe some JS files are slowing down downloading page?
Last step is to install XDebug and run your login with XDEBUG_PROFILE parameter and then use KCacheGrind tool to see what is happening during login and what takes most time.
(Check manual)
I would like to use magnific popup for a site which is still in development, but unfortunately nothing happens after the installation and adding the static content in my template.
No matter what i try no popup comes up.
If someone would like to help me i will provide access to the site.
Thanks a lot!
First thing to do:
look at your source code: does the 'link' show any sign of 'magnific popup' code?
Added classes? id?
Second: do you see any extra javascript and/or stylesheet that is added by the extension?
If you answer negative to 1 of these, the extension does not output anything. Sounds logic, but it is the first step. Is it a solution? Nope, it means your live just got a bit more worse, but hang in there !
If it does show any code from the ext: look at your console, are there any js errors occurred ? (if you don't know what console is, or (even worse) you work with IE) please read about chrome console of at least install Firefox with firebug.
My best beth would be a JS error...
Can it be possible that the ext itself does not work?
Does your php error logs tell you that the extension is behaving badly?
Do you see errors in the typoscript analyser (or whatever it's called to analyse the css_styled_content and other TS spaghetti )
If not, then no, it is not the ext.
Again, i'm betting my wive, three horses and a barrel of beer on JS erros.
Good luck mate !
ps: IF i'm wrong, i'm not sending you my wife by postal service. Loads of trouble last time. Nor the horses, same shizzle ..
In the past I had successfully created several Google Earth tours complete with audio and animation. As best I can remember, I looked at one of my tours 2weeks ago? and things were working fine.
But I look at the tours now on both my local machine and my host web server and the google earth tours have disappeared. When I look in firebug at where the code should be, I see the following error:
Failed to process gadget http://code.google.com/apis/kml/embed/tourgadget.xml. Reason: Unable to retrieve spec for... code.google.com/apis/kml/embed/tourgadget.xml. HTTP error 404
I have not changed anything within my code, so am completely at a loss.
Can anyone share what might have happened or what I need to do to get my GEs going again?
My web site is www.kavelookout.com...See www.kavelookout.com/fingers.html for where a tour should be.
UPDATE:
I believe this is the GE tour gadget code I need...
http://www.gmodules.com/ig/creator?synd=open&url=http://code.google.com/apis/kml/embed/tourgadget.xml
but as you can see, clicking on the 'More info...' link takes me to... google.com/ig/directory?synd=open&url=http://…
Does anyone know why GE Gadgets is not working at this time? Or what link I should be using to embed GE Tours? Can anyone confirm that GE Tours are having a problem, or is it me?
Much Thanks,
k
You should notice that the pages you're trying to process are no longer available, so, that's the nature of the error.
Check the link, it sais that the page is not being found, that's why you're getting a 404 error.
So I figured it out.
The embed code that was generated in the past was...
script src="http:// www.gmodules.com/ig/ifr?url=http://code.google.com/apis/kml/embed/tourgadget.xml
I'm not sure why or when it changed, but I found that the GE Tour gadget at this URL...
http://www.gmodules.com/ig/creator?synd=open&url=http://dl.google.com/developers/maps/tourgadget.xml
...now generates this new embed code...notice the differences...
script src="//www.gmodules.com/ig/ifr?url=http://dl.google.com/developers/maps/tourgadget.xml
Again, I'd love to know why things changed, but am happy to know there is an answer.
I have applications which are displayed as tabs in Facebook pages which have been working fine. They suddenly started displaying this output in the tab:
/1336720089,176820405/
if (window.CavalryLogger) { CavalryLogger.start_js(["EgxV3"]); }
__d("UFIUpdate",
Any ideas what is going on???
Here is a link to one of them: http://www.facebook.com/TweakShoes/app_132692060112327
A temporary solution is to add https:// to facebook itself. This doesn't solve the problem, but it'll allow you to see your page on a per client basis.
The best fix in the longer term until facebook fixes this issue is to go to your account settings > Security > Enable secure browsing. This will enforce HTTPS wherever it can and should resolve the issue for a lot of pages you're trying to access.
Good Luck!
After encountering this issue yesterday, I tracked it down to an apparent conflict with the JS log wrapper included as part of HTML5 Boilerplate's script.js file. In particular, the "make it safe to use console.log always" snippet. After commenting it out, the FB lib error went away and my app displayed properly.
I didn't dig into what the conflict was, but here is the snippet. If you use something similar on your page, then it may be worth investigating.
/* make it safe to use console.log always */
(function(b){function c(){}for(var d="assert,count,debug,dir,dirxml,error,exception,group,groupCollapsed,groupEnd,info,log,timeStamp,profile,profileEnd,time,timeEnd,trace,warn".split(","),a;a=d.pop();){b[a]=b[a]||c}})((function(){try
{console.log();return window.console;}catch(err){return window.console={};}})());
It's probably not a coincidence that FB's own logger bugs out with this.
Facebook has opened a bug for this issue and recently triaged it to medium priority - no word on when it will be addressed.