New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Official] Contentify 2 #52
Comments
Hello! Is Contentify 2 ready for fresh install? |
Hello. Yes it is. However, consider the current state being an alpha version. So it might have some bugs. (And ofcourse note that you have to switch to the |
Ok i make tarball 2.0-dev, then copy to /var/www now the install.php says: |
Okay. I start to hate this problem... I guess I should change the way Contentify decides if it is installed or not. However, the solution is to create an (empty) file: |
Okay now requirements page is shows but when click "Launch installer" its redirect to /install which empty (changing disable *.php from address just makes button Launch installer just reload page) so i go back to 1.1.0 and start my Laravel coding journey 😄 |
Okay. (However, this might be a problem with the server configuration so you might have it with 1.1 as well!) |
From where i can download contentify 2.0? |
Here: https://github.com/Contentify/Contentify/archive/2.0-dev.zip (Most likely you will have to create the |
Is there a live demo of Contentify 2? :) |
No not yet. Contentify 2 is a work in progress. Not final at all, not even a beta. Sorry if there was a misunderstanding. |
Hi. Thanks for verry good CMS! I'm trying contentify 2.0 and i'm getting this error:
|
Yep. Once it has reached a stable version ( |
Updated bug. Sorry :) |
Is there a file named |
Deleted. Getting same error. Log file says:
|
Okay I guess I know what happened, a bug in the installer. Bugfix: 09f5c73 Maybe the easiest way to get this bugfix is to delete everything then download the whole repository again from GitHub (it will contain the bugfix). Then install it again. |
Thanks! I will try! +++ |
Seems working perfect! But then i go to my profile i get this error:
:) |
Bug fixed: 1744e34 |
Thanks! I really like this CMS! BEST OF BEST! :) |
:) |
One more bug. After uploading a file, i get this error:
|
I uploaded several images but I did not see this error. |
Hello Chris. My edit: If file larger than 100mb or more i get this error. If file is small uploads working fine. (P.S: Uploading in .rar format) |
Okay. Please go to the admin panel. Then "Config", then "Diagnostics". What are the values of |
for me it is saying in install that PHP Mcrypt is not available but it is installed and up to date. Is there anything i have done wrong? |
Just to make sure I understand what you are speaking about: Does it look like this? http://i.imgur.com/BBQ0fds.jpg |
yes, i managed to fix that issue, but now i cannot run the install script. it says the file cannot be found in the public folder, so i tried using the wiki address http:// /contentify/install.php but did not work |
Hello @my-eternity, If i understand your request, you would upgrade Contentify 1.2 to Contentify 2 ? For Contentify 2 you must create ".installed" file in "storage\app" if you have installed it. |
I tried to do a fresh install of Contentify 2 and i tried to create the ".install" file in storage\app, after that i got a white screen. After i tried it again it said "NotFoundHttpException in RouteCollection.php line 161:" |
I'm not in my home, but I think it's ".installed" and not ".install" |
I just saw that i have to create that file in a comment.
|
Oh yes ^^ since this comment @chriskonnertz and @ImTheLe are change the .install to .installed for some reason ;) So now you are no problem ? :) |
oh..well.. :D |
can you create new issue please: https://github.com/Contentify/Contentify/issues/new |
hi |
Hello. Contentify 1.x uses Sentry, a library created by a company called Cartalyst: ttps://github.com/cartalyst/sentry
Therefore Contentify 2 uses Sentinel, the new version of Sentry. Sentinel helps to manage users, for example create user accounts and handle user permissions. In other words, it's a very important library. Unfortunately Sentry and Sentinel are not compatible at all. A website built with Contentify 1.x / Sentry will not work with Contentify 2 / Sentinel, because the user database table differs. That's the problem. The solution would be to create a migration path, an update tool that takes the old user data and transforms it so it would work with Sentinel. But this is a challenge. An expansive one. Expansive in meanings of effort and time. Contentify currently is a 100% open source CMS. It does not generate any revenues while it generates costs. Despite - as far as I know - being the only modern gaming CMS that is not in a beta with the release date "when it's done" (at some unspecified point in the future), Contentify is not very popular. I believe very few people would use such an migration tool. And this is where the story ends. I know that it sounds harsh, but writing such a tool is not worth the effort. Also, only solving the "Sentry vs Sentinel" conflict would just solve one problem amongst others. I am unhappy with how this went but this is one of the consequences of open source software: Sometimes there are not enough resources to meet all requirements. Side note: Contentify 1.x has long term support (LTS) so it will still get bugfixes after the release of Contentify 2. |
Hello Chris, FatalErrorException in Migrator.php line 335: is this error already solved? i felt sad after read your comment above, i really understand the situation. Thumbs up |
Hi
Did you try this? https://github.com/Contentify/Contentify/wiki/Troubleshooting#installation-error-message-fatalerrorexception-in-migratorphp
Well, yes and no. More information: #102
Yes it will continue, no worries. Next version will be 2.1 - see #113.
v1.2 but I recommend to use 2. It may have some bugs still but a) this is pretty normal for a new release and b) v2 is the future. Bugs will be fixed, updates such as v2.1 will be released.
Thanks! :) |
at the very first time, i used XAMPP to run this cms
Okay, for now i will use v2 and i'm very excited to wait the next release.
Thanks |
ErrorException in Collection.php line 1187: |
Hi, where does this error appear (URL for exmple |
Hi chris, i already configure the server.php and index.php into the right paths |
chris die fehler meldung kommt im backend bereich wenn man in die modul einstellungen möchte. |
Es scheint so, wenn man das CMS auf HTTPS umstellt, dass das backend System nicht auf HTTPS umgestellt wird. Bitte um Aufklärung. ;) |
Als Notlösung bitte eure .htaccess Datei ändern in folgendes: suche in deiner .htaccess Datei:
in folgendes ändern:
` |
Finally i figured out the problem my self. the problem appears when i uploaded pictures or images via backend. $app->bind('path.public', function() { and it works perfectly. |
Wie meinst du das? Was in der Tat stimmt: Wenn man HTTPS aktiviert gilt das nicht generell sondern im Grunde nur für den Login. Meinst du das? |
Notice: For other topics than bugs or problems with the installation, please use the v2.1 issue: #113 |
ja das meinte ich chris. Ich habe nun komischerweise ein neuen fehler gefunden: SQLSTATE[HY000]: General error: 1030 Got error -1 from storage engine (SQL: insert into |
@eodclan Hast du dazu noch mehr Infos? Wo tritt der Fehler auf bzw. wie kann man ihn erzeugen? |
Ich habe dasselbe Problem wie eodclan. `ErrorException in Collection.php line 1187: Undefined index: enabled
` |
Branch:
2.0-dev
Current Releases:
2.0
2.0 RC
2.0 Beta
Release Date:
24th of December, 2016. 🎄
Changelog so far:
Some bug fixes have been commited to Contentify 2 and 1.x. For examples changes that improve the compatibility with PHP 7 or a solution for the Twitch API issue.
Current issues:
The text was updated successfully, but these errors were encountered: