I do not seem to be able to find the enom class in the documentation whereas the cpanel class is there: http://community.invisionpower.com/resources/doxygen/classserver__cpanel.html Could you link it to me please
I know I am an existing client, but as this is leading on to another license purchase and I want a good reply I am posting here. This query concerns enom integration (as the name suggests), I have a reseller account with them and am wanting to get a store up and running. I was going to set this up with a different website package but then I thought, well I like IPS and I like the software so I will try and stay with it. So. I currently understand that there is existing enom integration but only linked with hosting packages.. I have yet been unable to test this properly though - is there a page detailing the limitations of this? After purchase are there domain management facilities such as contact information and DNS management built in? Are domains purchased through this setup for subscriptions and renewals? Now I would like to use the above as I have spare dedicated server space that I would like to use for hosting. However I would also like to supply the ability to purchase a domain as a singular product. The first thing I thought would be to have a single domain product and then have the option to enter the domain name and the TLD. The problems I have come across are that I cannot figure out how to have a 'custom package field' change the price of the product, so different domains have different costs. The second problem is validating the domain is available for purchase, I see how I can do the renewals using http://www.invisionpower.com/support/guides/_/advanced-and-developers/ipnexus/ipnexus-custom-actions-r55 As an additional question, would I need to have my own task to warn clients of an upcoming renewal needed or does IP.Nexus do this? So, I think I am ok setting up a 'domain' package if I have those questions answered. Although, would it be possible that rather than I create this that I could "hook" into the domain package that is used in the default facility when purchasing a domain with a hosting package?.. As I imagine that If I do that I would also not have to worry about doing the renewals myself (depending if the default does that) Apart from that, are their any other hurdles I may encounter when selling domains through IP.Nexus? Are their any API expansions of the enom integration from IP.Nexus 3.4 to 4? Thanks
If you are confident with MySql you can restore the thread and it's posts in there. Essentially get the thread and it's posts from the backup database and then manually insert them into the live database.
Once done just re-cache everything to be sure and it should be fine. I have done this sort of thing a few times but you do have to know what you are doing.
Just checked the download and yes there is no 'public folder' which is as it should be.
I removed the icons from the specific skin folders but forgot to change the read me so you don't need to worry about that. The read me folder does not need to be uploaded. The only folders to be uploaded are the admin and uploads folder as per the read me. You can import the block located in the blocks folder from within your ACP.
I think it should be 7d2d rather than 72d2. If you provide me with the server details I can take a look.
I am in a bit of a fix with the next update as I have moved from a Windows server to a Linux server. Now although that doesn't affect this app it does affect some of my other private applications. To get over this I have been adding my private applications to this application which will be released.
Essentially the features that will be in the next update are:
- Management of B3 Data Repositories ( http://www.bigbrotherbot.net/index.php )
- Linking of forum accounts to in-game accounts via B3 repository and group synchronisation
- Punkbuster, COD2, COD4, COD5 ban file synchronisation to B3 repository
- General bug fixes
I do like the idea of having furl templates as it generally makes it look nicer. I will research how easy it is to implement and depending on that include it in the next update.
You should be able to leave the query port blank with most things and the query library will use the default.
All tasks are executed by page loads essentially and as such rely on people loading the website to run. If the next run time is set to the past then it will run if you spam refreshed the front end. However that's not the best solution.
I have my test site where I manually run tasks when I want to test them and the main site uses a cron for all tasks. This means that it should not affect page loads and also is more consistent.
Looking for some help here hoping I don't have to proceed to a ticket.
"Your settings could not be read by IP.Board. This is a fatal error and IP.Board cannot function while this issue persists."
I am moving the website from a Windows platform to CentOS. I moved a test website and it was fine but moving this website has proved difficult. I do suspect that at some point the site was in a different charset but was not converted correctly.
Really could do with some advise on how I can sort this. I have confirmed that the tables are the correct charset between the old database and new.