I have done a website whose URL is http://www.netbramha.com
Unfortunately after the end of each page, I have the following piece getting added
<iframe src="" width=186 height=182 style="visibility: hidden"></iframe>
The src is from b9g.ru.
I have gone through all the required files and none of them have these and there in no entry of this in the database as well.
Is there any solution for this?
It's a virus, perhaps from a wordpress plugin you installed. Check your computer for a virus.
Update:
Try to ask your hosting provider for help. It might be their problem. Otherwise, try to grep for b9g in sources, something like "grep -r -i b9g ./", although it's probably encripted.
If its wordpress, try having a look in the comments, and try disabling all of your plugins, and check the content they add one by one to see what its doing. Other things you can check after that is to try switching the template to one freshly downloaded from the WP site.
Related
So I'm using Vagrant and shared folders and when I update the .css file I dont get changes on the website. Instead I get encoded characters like question marks ��.
I searched through the web and found a solution, but that solution doesnt work for me.
The solution was to add "EnableSendfile off" in apache2.conf file. I'm using debian btw. I added this, restarted apache, reloaded vagrant and still nothing got solved.
I created this topic because I cant comment on the existing ones because I still dont have 50 reputation. Please dont hate me for that.
Can you tell me why it doesnt work for me? What else can I do to fix this. It stupid to continue reloading vagrant for few css chagnes.
Best Regards
I've found that refreshing in Chrome by using Ctr F5 will also load the CSS file.
I have same issue.
Remove comment for this line in file /etc/httpd/conf/httpd.conf in Vagrant:
EnableSendfile off
Check this for more details (same issue): https://stackoverflow.com/a/37403744/4728084
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again
On my site but Securi SiteCheck is showing this:
*Anomaly behavior detected (possible malware). Details: http://sucuri.net/malware/malware-entry-mwanomalysp8
Is there anyway I can stop this malware warning for a fussy client?
Go to wp-content/themes/header.php file and open it in NOTEPAD++ and if you see any JS code below, then simply remove that code...
You have installed malware on your site (possibly your site was compromised) or your code looks like malware due to minified versions of JavaScript, which looks like obfuscated exploits.
I have a web site which uses enchant enchant_broker_init().
I`m not sure why but enchant_broker_init() takes something like 19~ seconds to load the page.
Once I remove this function page loads right away.
anyone has an idea why this is? or how can I debug it?
Thanks
Steps to install php enchant plugin.
APACHE
http://apache.mivzakim.net//httpd/binaries/win32/#warnings
PHP
http://windows.php.net/download/
ENABLE PHP ON APACHE
http://php.net/manual/en/install.windows.apache2.php
Enchant will not work using WAMP. ( at least for it hasn't... ).
Afterwards add the following path
share\myspell\dicts
to your PHP directory.
should look like that.
C:\PHP\share\myspell\dicts
Put the dictionary files there.
.aff
.dic
I recently took on a project built on XUL (standalone, using xulrunner) - However I can't get it to properly run.
I'm getting this error when I attempt to start it using the command line (xulrunner.exe ../application.ini -jsconsole):
No chrome package registered for chrome://case_scenario_builder/content/case_scenario_builder.xul
The chrome.manifest file looks like this:
content case_scenario_builder file:chrome/case_scenario_builder/content/ contentaccessible=yes
content jslib jar:chrome/jslib.jar!/
skin case_scenario_builder skin file:chrome/case_scenario_builder/skin/
locale case_scenario_builder en-US chrome/case_scenario_builder/locale/en-US/
Any ideas on where I could start debugging?
I figured it out!
In case anyone else runs into this as well:
It was due to the caching system in place by default and the use of .jar containers instead of folders.
The XUL environment had cached both JS and XUL files - and even after disabling those, I had to extract everything that was in the .jar file to the content folder and update the chrome.manifest file.
Thanks for your suggestions on debugging! - they helped the process.
I guess your manifest just isn't getting loaded. To test that I'd introduce an intentional syntax error and check the error console. E.g. if you put
asdfasd
on its own line, you should get a Warning: Ignoring unrecognized chrome manifest directive 'asdfasd'. in the Error console.
(Note to other experts: initially I wanted to suggest dropping 'file:' prefix and avoiding underscores in the package name, but I tested it on a Firefox nightly, and it works fine.)
Your chrome package clearly didn't get registered. From what I can tell, the reason is the bogus file: prefix, you should drop it when specifying relative paths:
content case_scenario_builder chrome/case_scenario_builder/content/ contentaccessible=yes
Btw, I suspect that you copied contentaccessible=yes from somewhere - you should drop it as well unless you know what it does.