Could it be that PHP short tags are not enabled in php.ini?
Looks like <?= syntax required it until PHP version 5.4?
3 possible fixes:
update php to 5.4 or better
update your code to use <?php instead of <?=
update your php.ini file to enable short_open_tag
For my money, #1 is the best as everyone should be on 5.6 (or 7 if possible).
openssl_verify is a PHP function, so you need to install it for PHP, normally it's installed as standard, so guess you're using an abnormal PHP installer...?
Here's a reference to a bug report that was created.
It may be as simple as you've not got the php.ini module line uncommented:
PHP OpenSSL Installation reference.
Firstly, when you say "theme" I am assuming you mean a set of templates.
There are a few ways to approach this.
Copy your entire local installation to the remote server
If you have the site working on your local machine and simply want to now put it on a remote server then you do not need to run the installer on the server. You can copy the files ...
I had a look at the link you posted. The error appears to be a different one.
"No database connection settings were found in the database config file."
Did you follow the official instructions: http://goo.gl/wX84vq ?
Usually you get the error you've mentioned if ExpressionEngine has not been installed yet. This appears to be the case. Please visit http://...
I have no idea! Kind of...
If your RackSpace server functions essentially like a VPS or bare metal machine (just in the cloud), then you're all set! There are a couple way to go about it. I'll explain a couple of simple ways this works on a regular VPS or bare metal machine.
You have your web root and an EE installation working on it. One way to go is ...
I have the same issue. What I did is to manually create these fields on Visitor Fields group:
[Field Name | Shortname | Field Type | Options]
Member account | member_account | visitor | n/a
Firstname | member_firstname | text | n/a
Lastname | member_lastname | text | n/a
Gender | member_gender | radio | 'Male' & 'Female' on Radio options
Birthday | ...
According to ExpressionEngine Licence it allows you to do copies for 2 purposes:
You may make copies of the Software for back-up purposes, provided
that you reproduce the Software in its original form and with all
proprietary notices on the back-up copy.
An ExpressionEngine license purchase allows a single “...
CSPRNG stands for cryptographically secure pseudo-random number generator which is a library added to PHP from version 7.0 onwards. From version 5.2 onwards it was possible to install an additional module on your server to provide this service.
So my guess is that the php system on the server you are using is running some flavour of php5, and that this ...
Your best bet is to open a support ticket with HostGator and asking them to 'whitelist' those mod_sec rules that are causing the problem. As EE5 isn't as common as say WordPress, most hosting providers therefore don't have the relevant rules whitelisted as they don't have clients that have run into the issue (yet).
If you ask them nicely they might be able ...
The only timeI've encountered something like this is when the site was on a shared hosting. It turned out this happened because of a leaky joomla install on that same server. You can safely delete the file. It's always best to update EE anyway. Just make sure to check if there aren't any more suspicious files on the server, or that files like admin.php/index....
Never ever do direct EE1 to EE3. First of all upgrade EE1 to EE2. That will make necessary changes to your database. (Remember change all the plugins with EE2 version otherwise backend and/or frontend may crash.)
After upgrading it to EE2, upgrade your server then upgrade site to EE3.
Always take a backup copy of your site.
Its good to ...
This ended up being simple. For my instance, the MySQL module wasn't installed for PHP. Once it was added it worked as expected... My issue ended up being the fact that the error was completely non-descript.
As long as you have a valid license, there is no issue with duplication. Just use the license for your development environment, and push it to the production environment. If you already have production set up, just clone the repo to your development environment.
EllisLab is not made up of monsters; many people run EE applications with a duplicated ...
You will need to make sure the folder you place in the third_party directory matches the package name.
From the Github repo, you can see that the files are called xxx.flag_master.php, so therefore the directory needs to be named flag_master. I assume the because the Github repo is called flag-master, the folder is being named that instead.
What we usually do is add a folder ee/ to the root and install everything there. The base url will then be http://yoururl.com/ee/ and ExpressionEngine will install everything accordingly and will ignore the subdirectory in segments.
When you go live (switch to the root directory) you will have to update the urls in General Configuration as well as any urls ...
Since posting my question, I haven't figured out why this happened, but I did come up with a workaround for it:
Import your upgraded production environment's MySQL database on your local environment*
Follow the update instructions from EllisLab up to but not including step 6.
Change $config['app_version'] in system/expressionengine/config/config.php to 292
Something similar - possibly a plugin not responding. Remove third-party plugins in your system folder, try updating again and then return your plugins...you should update fine, and then you'll need the third-party items back in to open the control panel.