Skip to content
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

Wsat generating wrong urls #668

Closed
sicutdeux opened this issue Apr 17, 2018 · 4 comments
Closed

Wsat generating wrong urls #668

sicutdeux opened this issue Apr 17, 2018 · 4 comments

Comments

@sicutdeux
Copy link

Everytime the Wsat has to render a New page, i get redirected to this kind of url:

wsat,TWsatGenerateAR

But if i use the proper url manually it works.

Version: latest composer project

@ctrlaltca
Copy link
Member

ctrlaltca commented Apr 24, 2018

Hi! I just tested creating a new project, adding this configuration to the application.xml:

<service id="wsat" class="System.Wsat.TWsatService" Password="pass">
  <modules>
    <module class="System.Data.ActiveRecord.TActiveRecordConfig" EnableCache="true">
      <database ConnectionString="mysql:host=localhost;dbname=db" Username="user" Password="pass" />
    </module>
  </modules>
</service>

I can now login to Wsat and generate the ActiveRecord classes correctly.
The url of the page used to generate the classes is indeed http://127.0.0.1/testapp/wsat,TWsatGenerateAR, where testapp is the name of the folder containing the test application.
The request module should be able to understand that "wsat" is a service name and "TWsatGenerateAR" is the requested page name for that service, and it seems to work here.
Can you please add some more details about your problem?

@darthdaniel85
Copy link
Member

Hi Fab, its been a long time... but Im back, this time from Los Angeles, USA. Glad to see that quite a few people are using WSAT. I will make some time to continue supporting Prado... also glad to see that you are still keeping the framework alive, thats remarkable. Greetings Daniel(WSAT creator)

@ctrlaltca
Copy link
Member

@sicutdeux did you manage to fix your issue?

@ctrlaltca
Copy link
Member

No news is good news, i suppose.
Pleas reopen if you still have this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants