a bit of a weird
On every page except my homepage I have "Authentication: no" showing in the Symfony, but when I check other pages I am logged in as expected.
I have tried clearing cache, session, and logging in and out and it remains. I discovered this from printing app.user as I'm using it in if statements.
I have also watched logs as logging in but everything is working fine!
I'm not sure how else to debug this - I also have this issue on my production server so I'm sure its application based
if anyone can suggest anything I would appreciate the thoughts/help
thanks
Try to change you security.yml file from:
sylius.security.shop_regex: "^/(?!admin|api/.*|api$|media/.*)[^/]++"
To
sylius.security.shop_regex: "^/(?!admin|api/.*|api$|media/.*)"
I'm using Sylius 1.1.1
Did you remove the localised urls? Please check the sylius.security.shop_regex settings:
http://docs.sylius.org/en/latest/cookbook/disabling-localised-urls.html
Related
I am testing/learning how to send info from a Gravity form to a test file on my website.
I am using a testfile.txt that I added in var/www/ which is the location of the Wordpress directory.
The command I am running updates that file and I am able to see its contents when i go to the domain: mywebsite.com/testfile.txt.
The first time I run the Gravity form, I can see the changes on the webpage. However, after updating its contents to something else, the webpage does not update despite reloading it.
To troubleshoot this, I SSH'd into the server to see if the file was being updated and indeed it was...
So, basically, the file is being updated on the server but not on my GoDaddy domain... Has anybody encountered a problem like this? And if so does anyone have a solution?
I am no Expert in this field, Beginner to be honest. When I was learning Python flask a framework for building website, I had similar issue. Maybe the problem is that, when you visit your website it loads from the cache. To solve that press 'ctrl + F5', it forces a cache refresh, and will guarantee that IF the content is changed, you will get the new content. Again, I am beginner myself.
As #Sadman said, whenever I don't see my content getting updated I do a hard refresh or delete the cookies and cache manually. Either one of these solved my problem. To make a hard refresh press ctrl+shift+r or ctrl+f5 or shift+f5 on windows. On MAC this is cmd+R. I hope this helps!
There seems to have been a technical problem. Please click the back button, refresh your browser, and try again.
I am facing this error on the standard /admin login form (used for logging in to the CMS).
I have done the upgrade (3.1>3.5), after that upgrade this form was working fine for a while but then it stopped working and started throwing
"There seems to have been a technical problem. Please click the back button, refresh your browser, and try again."
Upon investigation found, the Form.php in the framework class is throwing this error. Please note the framework version is now 3.5.4
Any help/pointers if someone faced the same issue upon upgrade ??
Thanks
I would try a dev/build?flush=all. I'm pretty sure that the Member class has had additional fields added after 3.1
You can always put your site in dev mode to see the errors.
I am building a Symfony2 project, using FosUserbundle and have a serious security issue. When a user tries to connect, it correctly redirects to the home page when the credentials are correct, but most of the time without actually loading the user, still with the anonymous token, not logged.
It sometimes logs me successfully at the first try, usually after 2-4 attempts, sometimes more. It seems to fail 70 to 80% of the time.
There is no error message at all, everything seems to work just fine, except it doesn't. I cloned my project without FosUser, using the login and security system in the cookbook in the documentation on the Symfony website, still the same.
The application has been developed with Symfony 2.3, but upgrading to 2.6 and 2.7 doesn't solve the problem.
The security code is completely vanilla except to extends my template in one twig file, and the behaviour is still the same without the extends.
The config files have been modified according to the FosUserBundle doc.
I am obviously missing something, but no idea what.
After a couple of week, it stopped doing weird stuff, that is good, but no idea why, that is not so good.
As i have said, the config files are straight out off the official doc. If they were at fault, i think that dozens would have had the same issue.
For the curious, it started doing weird stuff while i was playing with websockets and Ratchet. I don't know if it give an idea to someone as to the why.
I am currently building a website using drupal 7.x. Unfortunately I cannot seem to enter the admin/config page. Every time I click on the configuration tab on the administration menu, I only get a blank page. Then I created another sample site. It also has the same problem and I am using WAMP server. I cleared cache and finds no difference. I have searched for similar issues, but could find none. Can someone please tell me what I am doing wrong?
A number of things can cause the White Screen of Death, but the most common things to check:
As suggested above, memory limit may need to be increased.
Have you enabled any modules other than those in Drupal core? Try disabling contributed modules and enable individually until you experience the error, to help you identify which module is causing trouble. If you can't access the modules admin page, you can disable them in the database - the system table has a 'status' field. 1 means enable, 0 is disabled.
Could it be a permissions issue? Check admin access permissions or try logging in as the superuser (user ID 1).
Lots more and discussion here and here.
Finally I got the answer. Increase the max_execution_time in php.ini file. It solves the issue.
A few things to try...
Check your php error log for clues.
Create a simple file that calls phpinfo() and see what your memory_limit is. It may need to be increased.
Try tweaking your php.ini to get it to display an error message instead of a blank page.
I tracked this very issue to l10_update module, once I enable it, admin/config shows the WSOD. Once I disabled it, everything's fine. So:
- unchecking the localization_update module in the "modules" list
- de-installing it from the modules list
- deleting directory sites/all/modules/l10n_update
- and re-installing the module (from the same tar.gz file)
Source: https://www.drupal.org/node/1141160
Please see my DNN Forum Post for more details.
I've never had any issues with DotNetNuke installations. But with the new v5.20 (or v5.02, whichever it really is), everything runs perfectly fine through installation. I then get to the main default portal homepage. But as soon as I click any of the links available to continue (Home, Register or Login) I get 404 errors every time with a reference back to the applicable aspx page (Home.aspx, Register.aspx or Login.aspx.).
Windows 7, IIS7, SQL Server 2008. All permissions are setup properly on the directory and in IIS. I would think this is an IIS7 configuration issue, but I've tweaked everything in there a half-dozen times. No one at DNN is returning answers on my forum post anymore either after one guy tried.
Help!
This is something to do with the Friendly URL stuff. I found this blog post which talks about the Friendly URL Provider architecture. This made me try changing the urlFormat attribute for the DNNFriendlyUrl provider from "humanfriendly" to "searchfriendly", which made the URLs the way they used to be. I'm not sure exactly where things are going wrong and don't really have time to dig into it at the moment, but hopefully this will be helpful to get you moving again too.
With the release of DNN5 (up until 5.02.01 as of the time of writing), the friendly URL provider won't work when DotNetNuke is not on default port 80. There are different solutions floating around, but the simplest is just to replace the DNN friendly URL provider with the free one from iFinity. The installation is really simple and included in the download. Or see the following blog post:
http://www.sailer.com.au/dotnetnuke/dnn5-friendlyurl-port
Okay have you tried the 'old style' of login - domain.com/default.aspx?ctl=login
If that still doesnt work then i have to say that most likely something has happened to IIS - if so then you might just see if you can install the package you have on a different box or have a friend try a different box
I have done 2 upgrades with 5.2 and a few test installs with the Starter Kit Package and Install packages and have never seen this problem - not to say that it doesnt exist.
My next trial would be to go and redownload the install package from CodePlex and start from scratch to see if you can make the same thing happen again.
OKayone thing I dont think that has been mentioned in reading through everything is double check IIS.
My first guess without looking on your server would be to check if something happened to the 'check file exists' setting - i know this is changed in IIS7 so I cant point to the exact place to check this.
Here is a link to the IIS7 forums on it - http://forums.iis.net/t/1092696.aspx
http://forums.asp.net/t/1191083.aspx
either one might help - google also has a lot on this
Tell me how this goes in checking up on it and we can move forward from there!
you probably need to reg_iis on the version(s) of asp.net that your IIS is going to support.
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx
If the right version is not set up then you will get the 404 error
So placing it under port 80 works, right?
Is there a good reason not putting it under that port?