Jump to content



  • Posts

  • Joined

  • Days Won


 Content Type 



IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog



Everything posted by GreenLinks

  1. Nay it is not the case , in fact many websites only choose to run on SSL because it is faster now.
  2. That used to be the case 4-5 years ago. I advise you to catch up with current server technology...
  3. I am on Ryan's side. I would love to see additional security implementations however what Diego suggests does no good.
  4. Now supply more information please , how far is the support , i doubt i will have chance to get rid of greenseo but i think you made my life way easier :)
  5. I hope this will never make into Ipb
  6. GreenLinks


    I am sorry but i am not using that application so i can't say anything about it.
  7. GreenLinks


    No there is no solution and we don't have any intension of adding a feature like this. it will slow down boards a lot.
  8. I think he is talking about URL Route Filters
  9. GreenLinks


    You can't remove id's . Id's are mandatory
  10. You are simply missing PHP mbstring , you should consult your host on fixing that.
  11. I still fail to see why your users are unhappy. Once you take a backup of your database , you should turn your site online and just do your tests. But if i am not understanding wrong , you keep your forum offline. Why ?
  12. Why do you have unhappy users ? You didn't run this tool on a live database right ? You shouldn't be that naive
  13. The more i study this tool , the more i see that there was not actual much planning put on this tool. The perfect senario that this should be designed and function should be as following : CREATE DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci; Second step is running the conversion. When conversion starts CLI script should ask us which DB to read from and then again ask us which DB to write to. Lets assume DB1 and DB2 as those defined tables. Script should read table from DB 1 -> Converts to UTF8 -> Inserts into DB2 with utf8_general_ci This way when the conversion is done , boards will not have to wait for the second step current Convertor is running ( Altering collations on tables ) This would be way safer method to follow and things would run twice faster then current method. It is still not to late to correct this minor planning mistake. I strongly suggest IPB team to make changes so even the convertor will be perfect and can be completed twice faster then it currently is.
  14. One more info Rhett , Non converted tables ( ones that has x_utf_ prefix are usually related to IP.Convertor related )
  15. Yes , however that was when we first noticed the time out issues. Another thing i noticed is those timeouts specifically occur when you use 4-byte UTF-8 Encoding. On my mac pro total time to complete the conversion is around 5 hours vs 8 hours on test server but the difference was Use 4-byte UTF-8 Encoding Merts-Mac-Pro:GcForum lizardking$ php utf8convert/cli.php ------------------------------------------ Welcome to the IPS UTF8 Conversion utility ------------------------------------------ 303 table(s) are not UTF-8 and need converting. Use 4-byte UTF-8 Encoding (utf8mb4)? Some non-common symbols (such as historical scripts, music symbols and Emoji) require more space in the database to be stored. If you choose 'no', users will not be able to use these symbols on your site. If 'yes', these characters will be able to be used, but the database will use more disk space. [y] Enter 'y' for Yes [n] Enter 'n' for No n This utility will convert all the tables in this database to UTF-8. The converted data is inserted into new tables prefixed with x_utf_ and the original data kept. Press enter to continue Processing: 100% Conversion has completed in 2 hour(s), 24 minute(s) and 47 seconds. [f] Enter 'f' to finish [x] Enter 'x' to reset and start the conversion again. f You can now test the conversion by: Editing conf_global.php to add $INFO['sql_charset'] = 'UTF8'; Change $INFO['sql_tbl_prefix'] to: $INFO['sql_tbl_prefix'] = 'x_utf_'; If you are happy with the conversion, you can have it permanently rename the tables so that you can restore your original 'sql_table_prefix' and delete the original tables. [y] Enter 'y' to rename your tables [x] Enter 'x' to reset and start the conversion again. y Renaming tables, this may take a short while. Checking and fixing collations. You can now complete the conversion by editing conf_global.php to add $INFO['sql_charset'] = 'UTF8'; and to change $INFO['sql_tbl_prefix'] to: $INFO['sql_tbl_prefix'] = ''; I still have all the orig named tables which is clearly a sign that the convertor only received minor corrections.
  16. Sure lets report some bugs which are mainly highlighted in the ticket already : Timeout after huge table conversions Script fails to remove orig. named tables which doubles database sizes ( requires manual work , unacceptable ) Indexes are deleted during the conversion These are explained in the ticket ( expect indexes ) but we don't know if they are fixed or not . I did a final test after yesterdays upgrade ( all bugs unfortunately still exist ) Each test takes around 8 hours so if you are expecting us to go on with these tests , then you shall first act and implement improvements that will ease our job.
  17. If the team doesn't make necessary changes to assist big board owners within their tests , then highly possible we will stop reporting the bugs Aiwa. This conversion process needs to be flawless, thats why it shall include the most effective test practises which lays on having all changes on separate databases. I am sorry but i seriously don't see a reason how you can arguing against this. Math is extremely simple here and the outcome is again extremely simple. If anything goes wrong : If conversion done on a separate database : Dropping the secondary database - creating a new database takes : 2 min max If conversion done on same database : Multiple choices Clean the current database -> 60-90 min manual work Drop your test database, create a new database and first import your backup -> At least 60-70 minute wait time
  18. If anything goes wrong within the convertor example ( on our last test conversion we found some table renaming missing ) , you basically need to start from scratch or manually have to rename all those tables. Which is another major time consuming thing UTF8 Convertor should work as simple as possible and should not interfere with the main database. That shall always be the principle.
  19. Hello , Convertor may work for small websites in current state but for big boards it is not feasible. Current format risks too long down times for any big board. The tables are being forced to be created on same database. So if anything goes wrong big boards need to drop their database , reimport the database and start from scratch. Exporting a database takes around : 15 min Importing a database takes around : 1 hour Conversion is completed around : 2 hour 30 minute Collation change is taking around : 5 hours to compete You need to make sure to eliminate the need of exporting and importing the databases so we will not have to be forced to take down our boards longer then it is needed. If we assume upgrade is going to take around 2 hour ( table changes etc. ) IPB teams main focus should be on making sure no additional senario's can cause downtimes. So allowing a separate database should be the first target atm...
  20. Mark please consider the suggestion of separate database tables before gold release.
  21. Your suggestion makes sense from a point. Why reinvent the wheel . However there are major problems with that approach for many different cases. For example look at Magento , they need to use a heavily customised Zend version and have to invest on Zend development also. Your suggestions may sound perfect choice for your own usage but from my stand point suggested frameworks by you are really not great choices. They all have major flaws in my opinion and i personally stay away from any script that is build on those frameworks. As you can see your argument will not even hold against another regular customer. The team is responsible with developing IPB. They were hired because IPB management felt they are good developers. So instead of trying to teach them their job , why not await what the team will bring to the table and then voice your opinion ?
  22. Hey Matt , A very important observation. Strongly suggest you to consider adding an option to keep data in a separate database instead of the same one. The conversion maybe completed fast though final table alterations are killer for any board out there. Checking and fixing collations takes around 5+ hours and still on reputation_cache table. I expect we have at least 2 more hours to complete.
  23. I see no reason to run web version :)
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy