Updating vbulletin

We had to do quite some changes for the second import, so we’re going to see if we had any regressions, and do the first import over again to see if we broke something. Please register a mime type using `register_mime_type` then use `register_compressor` or `register_transformer`. ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/attribute_methods/dirty.rb:29:in `save! ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `block in save! ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in `transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `save! Now, onto the 301 redirects as we have a lot of content I found this If you’ve moved from other forum software to Discourse using one of our import scripts, then you probably want all your hard-earned Google search results to continue pointing to the same content.EDIT Here’s a prerelease https://gist.github.com/discoursehosting/579d63db25d3a2a0d9cac85d9465aeff loading existing groups... https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors (called from block in at /vagrant/config/initializers/100-sprockets.rb:17) DEPRECATION WARNING: Sprockets method `register_engine` is deprecated. ' from /vagrant/script/import_scripts/base.rb:423:in `create_category' from /vagrant/script/import_scripts/base.rb:393:in `block in create_categories' from /vagrant/script/import_scripts/base.rb:374:in `each' from /vagrant/script/import_scripts/base.rb:374:in `create_categories' from script/import_scripts/vbulletin5.rb:208:in `import_categories' from script/import_scripts/vbulletin5.rb:37:in `execute' from /vagrant/script/import_scripts/base.rb:45:in `perform' from script/import_scripts/vbulletin5.rb:634:in ` Hey @michaeld The import ran, the numbers are looking better however, I cant see any posts when i load discourse. 4852 / 4852 (100.0%) [445687 items/min] importing posts... 195 / 195 (100.0%) updating bumped_at on topics updating last posted at on users updating last seen at on users Updating topic reply counts... Discourse has a built-in way to handle this for you as an alternative to writing nginx rules, using the permalinks lookup table.

It is not free, unlike others such as php BB, PHPWind, or Vanilla, with licenses starting at 9 for v Bulletin 5.0 Connect, the latest version of the forum software.

If a single forum page has a size of 100 Kilobyte for example, you can deliver approximately 250,000 requests before the bandwidth runs out.

And that is not taking into account your own visits to the admin interface or bots that crawl the forum.

If I do get this figured out, I’ll try posting a walkthrough of what I did, so it’s available for anyone else. quick and dirty fix: just add 20 wherever you see 22 or 23 in the code. The Moderators category error is harmless, you can safely ignore it. 1060 / 5523 ( 19.2%) /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in `raise_record_invalid': Validation failed: Category Name has already been taken (Active Record:: Record Invalid) from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:43:in `save!

There’s currently no importer for v Bulletin 5 available. 40 / 40 (100.0%) updating bumped_at on topics updating last posted at on users updating last seen at on users Updating topic reply counts... ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/attribute_methods/dirty.rb:29:in `save! ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `block in save! ' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in `transaction' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' from /home/vagrant/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `save!

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating vbulletin”