Sorry to hit two lists, but I'm attaching some sample data for testing purposes that should make testing a bit more efficient by requiring fewer clicks.
You can just put it in the installation/sql/mysql folder and it will be picked up automatically when you install.
Hi Elin. Sounds good. I haven't tried it, and maybe I should before commenting, but can you expand on your description? i.e. How does it differ from default sample data? Which clicks does it save? Does this do anything to assist the ID=42 problem now that we're randomising? Peter.
I've attached a screen shot of the home page. It's different from the default sample data because it is designed for testers seeking to work efficiently testing the core features under various scenarios not for beginning users needing to be told that they should login to their new sites or how to find the admin :). If there are additional scenarios people want to suggest be included in the testing package please post them on this thread. Obviously this data set will change as things are added to allow testing of those things e.g. new templates. One thing I did was delete the site map so that means that we can more easily test items with no menu links anywhere in their history. I'll be tweaking it some more before alpha2, which is why feed back is welcome.
As i said in the tracker we'll have all the modified by values deleted by alpha2. So right now I'm working on a refresh of all including deleting the unused fields as mentioned elsewhere, dealing with the modified users/dates, cleaning up dates that have been changed since 1/1/11 and setting versions and hits back to appropriate values.
So one thing .. if you do make a patch for any of the sample data sets (I really don't recommend this but sometimes people want to anyway) it is very very important that you make sure that you reset any content records back to no modified by user and no modified by date and that you change the user id of the created_by user id back to 42 and the created date back to 1/1/11.
Please note that patches (if you want to make them anyway) should always be made by making the changes in the database and then dumping out the needed records, never by editing directly.
On Thursday, July 19, 2012 9:40:25 PM UTC-4, Peter Wiseman wrote:
> Hi Elin. Sounds good. I haven't tried it, and maybe I should before > commenting, but can you expand on your description? i.e. How does it > differ from default sample data? Which clicks does it save? Does this do > anything to assist the ID=42 problem now that we're randomising? Peter.
> So one thing .. if you do make a patch for any of the sample data sets (I
> really don't recommend this but sometimes people want to anyway) it is very
> very important that you make sure that you reset any content records back
> to no modified by user and no modified by date and that you change the user
> id of the created_by user id back to 42 and the created date back to 1/1/11.
On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
> Hi,
> Sorry to hit two lists, but I'm attaching some sample data for testing > purposes that should make testing a bit more efficient by requiring fewer > clicks.
> You can just put it in the installation/sql/mysql folder and it will be > picked up automatically when you install.
On Friday, July 20, 2012 8:46:30 AM UTC-4, Rune V. Sjøen wrote:
> I have only one word to describe this... Awesome!
> - Rune
> On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
>> Hi,
>> Sorry to hit two lists, but I'm attaching some sample data for testing >> purposes that should make testing a bit more efficient by requiring fewer >> clicks.
>> You can just put it in the installation/sql/mysql folder and it will be >> picked up automatically when you install.
I had posted my comments on dev-cms.
let me post them here:
One of the issue we got as testers/patchers for the 1.6/1/7/2.5 series was the fact that many options were not set to Yes in the Components Global Options, or if done, were overriden by the default menu items.
This has forced us into changing these settings for each new install, to be sure something was not broken when patching.
Example: all the Written by, Published dates, etc. for articles.
I suggest to correct the new sample data for these. I.e. set all parameters in menu items to Global and make sure general Options are set to display all possibilities
>On Friday, July 20, 2012 8:46:30 AM UTC-4, Rune V. Sjøen wrote:
>I have only one word to describe this... Awesome!
>- Rune
>On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
>Hi,
>Sorry to hit two lists, but I'm attaching some >sample data for testing purposes that should >make testing a bit more efficient by requiring >fewer clicks.
>You can just put it in the >installation/sql/mysql folder and it will be >picked up automatically when you install.
This e-mail and any attachments may be confidential. You must not disclose or use the information contained in this e-mail if you are not the
intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies.
-----------------------------------------------------------
Jean-Marie Simonet / infograf768
Joomla Production Working group
Joomla! Translation Coordination Team
I've just updated the pull request to fix an issue in mod_weblinks (thanks Jacob), if anyone is testing you may want to update to it.
Also in terms of core sql settings there is a proposal from Brian in the feature tracker to add a guest user group by default. I think that's a great idea and if no one has objections I'll make that sql modification.
On Sunday, July 22, 2012 3:56:01 AM UTC-4, infograf768 wrote:
> I had posted my comments on dev-cms.
> let me post them here:
> One of the issue we got as testers/patchers for the 1.6/1/7/2.5 series was > the fact that many options were not set to Yes in the Components Global > Options, or if done, were overriden by the default menu items.
> This has forced us into changing these settings for each new install, to > be sure something was not broken when patching.
> Example: all the Written by, Published dates, etc. for articles.
> I suggest to correct the new sample data for these. I.e. set all > parameters in menu items to Global and make sure general Options are set to > display all possibilities
> JM
> :)
> I've sent a pull request with updated data reflecting the field changes > discussed else where and that file also has the users cleaned up.
> On Friday, July 20, 2012 8:46:30 AM UTC-4, Rune V. Sjøen wrote:
> I have only one word to describe this... Awesome!
> - Rune
> On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
> Hi,
> Sorry to hit two lists, but I'm attaching some sample data for testing > purposes that should make testing a bit more efficient by requiring fewer > clicks.
> You can just put it in the installation/sql/mysql folder and it will be > picked up automatically when you install.
> Elin
> --
> You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group.
> To view this discussion on the web visit > https://groups.google.com/d/msg/joomlabugsquad/-/ikzBrquoGjkJ.
> To post to this group, send email to joomlabugsquad@googlegroups.com.
> To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com.
> For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
> --
> *Please keep the Subject wording in your answers*
> This e-mail and any attachments may be confidential. You must not disclose > or use the information contained in this e-mail if you are not the
> intended recipient. If you have received this e-mail in error, please > notify us immediately and delete the e-mail and all copies.
> -----------------------------------------------------------
> Jean-Marie Simonet / infograf768
> Joomla Production Working group
> Joomla! Translation Coordination Team
On Sun, Jul 22, 2012 at 7:50 AM, Elin <elin.war...@gmail.com> wrote:
> I've just updated the pull request to fix an issue in mod_weblinks (thanks
> Jacob), if anyone is testing you may want to update to it.
> Also in terms of core sql settings there is a proposal from Brian in the
> feature tracker to add a guest user group by default. I think that's a great
> idea and if no one has objections I'll make that sql modification.
> Elin
> On Sunday, July 22, 2012 3:56:01 AM UTC-4, infograf768 wrote:
>> I had posted my comments on dev-cms.
>> let me post them here:
>> One of the issue we got as testers/patchers for the 1.6/1/7/2.5 series was
>> the fact that many options were not set to Yes in the Components Global
>> Options, or if done, were overriden by the default menu items.
>> This has forced us into changing these settings for each new install, to
>> be sure something was not broken when patching.
>> Example: all the Written by, Published dates, etc. for articles.
>> I suggest to correct the new sample data for these. I.e. set all
>> parameters in menu items to Global and make sure general Options are set to
>> display all possibilities
>> JM
>> :)
>> I've sent a pull request with updated data reflecting the field changes
>> discussed else where and that file also has the users cleaned up.
>> On Friday, July 20, 2012 8:46:30 AM UTC-4, Rune V. Sjøen wrote:
>> I have only one word to describe this... Awesome!
>> - Rune
>> On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
>> Hi,
>> Sorry to hit two lists, but I'm attaching some sample data for testing
>> purposes that should make testing a bit more efficient by requiring fewer
>> clicks.
>> You can just put it in the installation/sql/mysql folder and it will be
>> picked up automatically when you install.
>> Elin
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! bug Squad" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/joomlabugsquad/-/ikzBrquoGjkJ.
>> To post to this group, send email to joomlabugsquad@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomlabugsquad+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomlabugsquad?hl=en.
>> --
>> Please keep the Subject wording in your answers
>> This e-mail and any attachments may be confidential. You must not disclose
>> or use the information contained in this e-mail if you are not the
>> intended recipient. If you have received this e-mail in error, please
>> notify us immediately and delete the e-mail and all copies.
>> -----------------------------------------------------------
>> Jean-Marie Simonet / infograf768
>> Joomla Production Working group
>> Joomla! Translation Coordination Team
> To post to this group, send email to joomlabugsquad@googlegroups.com.
> To unsubscribe from this group, send email to
> joomlabugsquad+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomlabugsquad?hl=en.
-----Original message----- From: Mark Dexter <dextercow...@gmail.com> To: joomlabugsquad@googlegroups.com Sent: Tue, Jul 24, 2012 17:18:27 GMT+00:00 Subject: Re: [jbs] Re: Sample data for testing
+1 here. Mark
On Sun, Jul 22, 2012 at 7:50 AM, Elin <elin.war...@gmail.com> wrote: > I've just updated the pull request to fix an issue in mod_weblinks (thanks > Jacob), if anyone is testing you may want to update to it.
> Also in terms of core sql settings there is a proposal from Brian in the > feature tracker to add a guest user group by default. I think that's a great > idea and if no one has objections I'll make that sql modification.
> Elin
> On Sunday, July 22, 2012 3:56:01 AM UTC-4, infograf768 wrote:
>> I had posted my comments on dev-cms. >> let me post them here:
>> One of the issue we got as testers/patchers for the 1.6/1/7/2.5 series was >> the fact that many options were not set to Yes in the Components Global >> Options, or if done, were overriden by the default menu items. >> This has forced us into changing these settings for each new install, to >> be sure something was not broken when patching. >> Example: all the Written by, Published dates, etc. for articles. >> I suggest to correct the new sample data for these. I.e. set all >> parameters in menu items to Global and make sure general Options are set to >> display all possibilities
>> JM
>> :)
>> I've sent a pull request with updated data reflecting the field changes >> discussed else where and that file also has the users cleaned up.
>> On Friday, July 20, 2012 8:46:30 AM UTC-4, Rune V. Sjøen wrote:
>> I have only one word to describe this... Awesome!
>> - Rune
>> On Thursday, 19 July 2012 20:45:33 UTC+2, Elin wrote:
>> Hi,
>> Sorry to hit two lists, but I'm attaching some sample data for testing >> purposes that should make testing a bit more efficient by requiring fewer >> clicks.
>> You can just put it in the installation/sql/mysql folder and it will be >> picked up automatically when you install.
>> Elin
>> -- >> You received this message because you are subscribed to the Google Groups >> "Joomla! bug Squad" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/joomlabugsquad/-/ikzBrquoGjkJ. >> To post to this group, send email to joomlabugsquad@googlegroups.com. >> To unsubscribe from this group, send email to >> joomlabugsquad+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/joomlabugsquad?hl=en.
>> --
>> Please keep the Subject wording in your answers
>> This e-mail and any attachments may be confidential. You must not disclose >> or use the information contained in this e-mail if you are not the >> intended recipient. If you have received this e-mail in error, please >> notify us immediately and delete the e-mail and all copies. >> ----------------------------------------------------------- >> Jean-Marie Simonet / infograf768 >> Joomla Production Working group >> Joomla! Translation Coordination Team
> To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
-- You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group. To post to this group, send email to joomlabugsquad@googlegroups.com. To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/joomlabugsquad?hl=en.
